document order (not character stream), nav-* properties at risk due to only one current known implementation.

Author: Tantek Çelik

css3-ui/Overview.html

@@ -55,12 +55,12 @@
    src="http://www.w3.org/Icons/w3c_home" width=72> </a>
    <h1>CSS Basic User Interface Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 October
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 30 November
     2011</h2>
 
    <dl>
     <dt>This version:</dt>
-    <!-- <dd><a href="http://www.w3.org/TR/2011/ED-css3-ui-20111029">http://www.w3.org/TR/2011/ED-css3-ui-20111029</a></dd> -->
+    <!-- <dd><a href="http://www.w3.org/TR/2011/ED-css3-ui-20111130">http://www.w3.org/TR/2011/ED-css3-ui-20111130</a></dd> -->
 
     <dd><a
      href="http://dev.w3.org/csswg/css3-ui/">http://dev.w3.org/csswg/css3-ui/</a>
@@ -261,11 +261,9 @@ <h3 class="no-num no-toc" id=atrisk>Features at risk</h3>
    see these features remain in this specification. All other features are
    either defined in a normative reference (e.g. CSS 2.1 <a href="#CSS21"
    rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> or Selectors <a
-   href="#SELECT" rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a>), or
-   dependencies for another specification (e.g. XForms <a href="#XFORMS10"
-   rel=biblioentry>[XFORMS10]<!--{{XFORMS10}}--></a>) or are believed to have
-   one or more implementations (perhaps experimental), and thus will not be
-   dropped without returning to last call.
+   href="#SELECT" rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a>) or are
+   believed to have two or more implementations, and thus will not be dropped
+   without returning to last call.
 
   <ul><!-- 
  At risk due to only one implementation, or obsolete dependency:
@@ -293,6 +291,14 @@ <h3 class="no-num no-toc" id=atrisk>Features at risk</h3>
  
  <li>ime-mode: new - not sure about IE5+ vs FF3+ interop
  </li>
+
+ <li>nav-index, nav-up, nav-down, nav-right, nav-left, properties
+ 		implemented for sure only by Opera, http://www.opera.com/docs/specs/presto22/#css
+ 		possibly obsolete: Tasman v1 internal implementation
+ 		possibly current: MSTV Tasman
+ 		required (depended on) by non-web DVB-HTML, ATSC standards
+ 		 - unknown if any DVB-HTML or ATSC simulators 
+ </li> 
  
  Not at risk:
  <li>CSS2.1:  		:hover :active :focus</li>
@@ -321,10 +327,6 @@ <h3 class="no-num no-toc" id=atrisk>Features at risk</h3>
  <li>pointer-events property:
     implemented by Firefox 3.6 and later, Safari 4 and later, Opera v?
  </li>
- <li>nav-* properties
- 		implemented by Opera, Tasman v1 internal implementation
- 		required (depended on) by DVB-HTML, ATSC standards
- </li> 
  <li>'resize' property
     implemented by Firefox 4 and Safari
  </li>
@@ -354,6 +356,15 @@ <h3 class="no-num no-toc" id=atrisk>Features at risk</h3>
    <li>&lsquo;<a href="#ime-mode"><code
     class=property>ime-mode</code></a>&rsquo; property
 
+   <li>&lsquo;<a href="#nav-index0"><code
+    class=property>nav-index</code></a>&rsquo;, &lsquo;<a
+    href="#nav-up"><code class=property>nav-up</code></a>&rsquo;, &lsquo;<a
+    href="#nav-down"><code class=property>nav-down</code></a>&rsquo;,
+    &lsquo;<a href="#nav-right"><code
+    class=property>nav-right</code></a>&rsquo;, &lsquo;<a
+    href="#nav-left"><code class=property>nav-left</code></a>&rsquo;
+    properties
+
    <li>&lsquo;<a href="#text-overflow0"><code
     class=property>text-overflow</code></a>&rsquo; property value:
     &lt;string&gt;
@@ -3745,12 +3756,12 @@ <h4 id=nav-index><span class=secno>10.2.1. </span>Sequential navigation
     element with the lowest nav-index value to the element with the highest
     value. Values need not be sequential nor must they begin with any
     particular value. Elements that have identical nav-index values should be
-    navigated in the order they appear in the character stream.
+    navigated in document order.
 
    <li>Those elements that do not support the nav-index property or support
     it and assign it a value of &lsquo;<code class=css><span
     class=value>auto</span></code>&rsquo; are navigated next. These elements
-    are navigated in the order they appear in the character stream.
+    are navigated in document order.
 
    <li>Elements that are disabled do not participate in the sequential
     navigation order.

css3-ui/Overview.src.html

@@ -185,7 +185,7 @@ <h3 class="no-num no-toc" id="crec">Candidate Recommendation Exit Criteria</h3>
 
 <h3 class="no-num no-toc" id="atrisk">Features at risk</h3>
 
-<p>The Working Group has identified the following features as at risk of being removed from CSS Basic User Interface Module Level 3 when exiting CR. Implementors are urged to implement these features, if they wish to see these features remain in this specification.  All other features are either defined in a normative reference (e.g. CSS 2.1 [[!CSS21]] or Selectors [[!SELECT]]), or dependencies for another specification (e.g. XForms [[XFORMS10]]) or are believed to have one or more implementations (perhaps experimental), and thus will not be dropped without returning to last call.</p>
+<p>The Working Group has identified the following features as at risk of being removed from CSS Basic User Interface Module Level 3 when exiting CR. Implementors are urged to implement these features, if they wish to see these features remain in this specification.  All other features are either defined in a normative reference (e.g. CSS 2.1 [[!CSS21]] or Selectors [[!SELECT]]) or are believed to have two or more implementations, and thus will not be dropped without returning to last call.</p>
 <ul>
  <!-- 
  At risk due to only one implementation, or obsolete dependency:
@@ -213,6 +213,14 @@ <h3 class="no-num no-toc" id="atrisk">Features at risk</h3>
  
  <li>ime-mode: new - not sure about IE5+ vs FF3+ interop
  </li>
+
+ <li>nav-index, nav-up, nav-down, nav-right, nav-left, properties
+ 		implemented for sure only by Opera, http://www.opera.com/docs/specs/presto22/#css
+ 		possibly obsolete: Tasman v1 internal implementation
+ 		possibly current: MSTV Tasman
+ 		required (depended on) by non-web DVB-HTML, ATSC standards
+ 		 - unknown if any DVB-HTML or ATSC simulators 
+ </li> 
  
  Not at risk:
  <li>CSS2.1:  		:hover :active :focus</li>
@@ -241,10 +249,6 @@ <h3 class="no-num no-toc" id="atrisk">Features at risk</h3>
  <li>pointer-events property:
     implemented by Firefox 3.6 and later, Safari 4 and later, Opera v?
  </li>
- <li>nav-* properties
- 		implemented by Opera, Tasman v1 internal implementation
- 		required (depended on) by DVB-HTML, ATSC standards
- </li> 
  <li>'resize' property
     implemented by Firefox 4 and Safari
  </li>
@@ -257,6 +261,7 @@ <h3 class="no-num no-toc" id="atrisk">Features at risk</h3>
  <li>'content' property value: icon</li>
  <li>'icon' property</li>
  <li>'ime-mode' property</li>
+ <li>'nav-index', 'nav-up', 'nav-down', 'nav-right', 'nav-left' properties</li>
  <li>'text-overflow' property value: &lt;string&gt;</li>
  <li>'text-overflow' property 2-value syntax and definition.</li>
 </ul>
@@ -2139,9 +2144,10 @@ <h4 id="nav-index">Sequential navigation order: the <span class="property">'nav-
 the element with the lowest nav-index value to the element with the 
 highest value. Values need not be sequential nor must they begin with 
 any particular value. Elements that have identical nav-index values 
-should be navigated in the order they appear in the character stream.</li>
+should be navigated in document order.</li>
 <li>Those elements that do not support the nav-index property or 
-support it and assign it a value of '<span class="value">auto</span>' are navigated next. These elements are navigated in the order they appear in the character stream.</li>
+support it and assign it a value of '<span class="value">auto</span>' are navigated next. These elements are navigated in document
+order.</li>
 <li>Elements that are disabled do not participate in the sequential navigation order.</li>
 </ol>
 <p>