hixie: Add some notes explaining why these are SHOULDs and not MUSTs. (whatwg r7001)

hixie: Add some notes explaining why these are SHOULDs and not MUSTs.
(whatwg r7001)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5591&r2=1.5592&f=h
http://html5.org/tools/web-apps-tracker?from=7000&to=7001

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5591
retrieving revision 1.5592
diff -u -d -r1.5591 -r1.5592
--- Overview.html 15 Feb 2012 23:23:29 -0000 1.5591
+++ Overview.html 16 Feb 2012 00:06:28 -0000 1.5592
@@ -320,7 +320,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-15-february-2012">Editor's Draft 15 February 2012</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-16-february-2012">Editor's Draft 16 February 2012</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -467,7 +467,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 15 February 2012 Editor's Draft.
+  This specification is the 16 February 2012 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
   actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
   group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -54782,6 +54782,11 @@
     be reached using sequential focus navigation, and if so, what its
     relative order should be.</p>
 
+    <p class="note">One valid reason to ignore the platform
+    conventions and always allow an element to be focused would be if
+    the user's only mechanism for activating an element is through a
+    keyboard action that triggers the focused element.</p>
+
    </dd>
 
    <dt id="negative-tabindex">If the value is a negative integer</dt>
@@ -54792,6 +54797,14 @@
     not allow the element to be reached using sequential focus
     navigation.</p>
 
+    <p class="note">One valid reason to ignore the requirement that
+    sequential focus navigation not allow the author to lead to the
+    element would be if the user's only mechanism for moving the focus
+    is sequential focus navigation. For instance, a keyboard-only user
+    would be unable to click on a text field with a negative <code title="attr-tabindex"><a href="#attr-tabindex">tabindex</a></code>, so that user's user agent
+    would be well justified in allowing the user to tab to the control
+    regardless.</p>
+
    </dd>
 
    <dt>If the value is a zero</dt>

Received on Thursday, 16 February 2012 00:07:30 UTC