[html5] r6128 - [e] (0) add more advice about weird focus ring cases

[whatwg at whatwg.org]

Author: ianh
Date: 2011-05-11 14:46:46 -0700 (Wed, 11 May 2011)
New Revision: 6128

Modified:
   complete.html
   index
   source
Log:
[e] (0) add more advice about weird focus ring cases

Modified: complete.html
===================================================================
--- complete.html	2011-05-11 21:41:10 UTC (rev 6127)
+++ complete.html	2011-05-11 21:46:46 UTC (rev 6128)
@@ -35807,7 +35807,11 @@
     focused from the mouse. Other platforms simply don't draw focus
     rings around some elements at all unless relevant accessibility
     features are enabled. This API is intended to follow these
-    conventions.</p>
+    conventions. User agents that implement distinctions based on the
+    manner in which the element was focused are encouraged to classify
+    focus driven by the <code title=dom-focus><a href=#dom-focus>focus()</a></code> method
+    based on the kind of user interaction event from which the call
+    was triggered (if any).</p>
 
     <p>The focus ring should not be subject to the <a href=#shadows title=shadows>shadow effects</a>, the <a href=#dom-context-2d-globalalpha title=dom-context-2d-globalAlpha>global alpha</a>, or the <a href=#dom-context-2d-globalcompositeoperation title=dom-context-2d-globalCompositeOperation>global composition
     operators</a>, but <em>should</em> be subject to the <a href=#clipping-region title="clipping region">clipping region</a>.</p>

Modified: index
===================================================================
--- index	2011-05-11 21:41:10 UTC (rev 6127)
+++ index	2011-05-11 21:46:46 UTC (rev 6128)
@@ -35835,7 +35835,11 @@
     focused from the mouse. Other platforms simply don't draw focus
     rings around some elements at all unless relevant accessibility
     features are enabled. This API is intended to follow these
-    conventions.</p>
+    conventions. User agents that implement distinctions based on the
+    manner in which the element was focused are encouraged to classify
+    focus driven by the <code title=dom-focus><a href=#dom-focus>focus()</a></code> method
+    based on the kind of user interaction event from which the call
+    was triggered (if any).</p>
 
     <p>The focus ring should not be subject to the <a href=#shadows title=shadows>shadow effects</a>, the <a href=#dom-context-2d-globalalpha title=dom-context-2d-globalAlpha>global alpha</a>, or the <a href=#dom-context-2d-globalcompositeoperation title=dom-context-2d-globalCompositeOperation>global composition
     operators</a>, but <em>should</em> be subject to the <a href=#clipping-region title="clipping region">clipping region</a>.</p>

Modified: source
===================================================================
--- source	2011-05-11 21:41:10 UTC (rev 6127)
+++ source	2011-05-11 21:46:46 UTC (rev 6128)
@@ -39673,7 +39673,11 @@
     focused from the mouse. Other platforms simply don't draw focus
     rings around some elements at all unless relevant accessibility
     features are enabled. This API is intended to follow these
-    conventions.</p>
+    conventions. User agents that implement distinctions based on the
+    manner in which the element was focused are encouraged to classify
+    focus driven by the <code title="dom-focus">focus()</code> method
+    based on the kind of user interaction event from which the call
+    was triggered (if any).</p>
 
     <p>The focus ring should not be subject to the <span
     title="shadows">shadow effects</span>, the <span