[html5] r8227 - [e] (0) Clarify rules for drawing focus rings Affected topics: Canvas

whatwg at whatwg.org whatwg at whatwg.org
Wed Oct 16 15:43:23 PDT 2013


Author: ianh
Date: 2013-10-16 15:43:22 -0700 (Wed, 16 Oct 2013)
New Revision: 8227

Modified:
   complete.html
   index
   source
Log:
[e] (0) Clarify rules for drawing focus rings
Affected topics: Canvas

Modified: complete.html
===================================================================
--- complete.html	2013-10-15 23:19:20 UTC (rev 8226)
+++ complete.html	2013-10-16 22:43:22 UTC (rev 8227)
@@ -256,7 +256,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 15 October 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 16 October 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -37232,7 +37232,16 @@
 
    <li><p>Return <var title="">result</var>.</li>
 
-  </ol><p>The <dfn id=dom-context-2d-scrollpathintoview title=dom-context-2d-scrollPathIntoView><code>scrollPathIntoView()</code></dfn>
+  </ol><p>User agents should not implicitly close open subpaths in the intended path when drawing the
+  focus ring.</p>
+
+  <p class=note>This might be a moot point, however. For example, if the focus ring is drawn as an
+  axis-aligned bounding rectangle around the points in the intended path, then whether the subpaths
+  are closed or not has no effect. This specification intentionally does not specify precisely how
+  focus rings are to be drawn: user agents are expected to honor their platform's native
+  conventions.</p>
+
+  <hr><p>The <dfn id=dom-context-2d-scrollpathintoview title=dom-context-2d-scrollPathIntoView><code>scrollPathIntoView()</code></dfn>
   method, when invoked, if the <code><a href=#canvasrenderingcontext2d>CanvasRenderingContext2D</a></code> object's <a href=#concept-canvas-context-bitmap-mode title=concept-canvas-context-bitmap-mode>context bitmap mode</a> is <a href=#concept-canvas-fixed title=concept-canvas-fixed>fixed</a>, must run the following steps; and otherwise, must add
   instructions to the <a href=#scratch-bitmap>scratch bitmap</a>'s <a href=#list-of-pending-interface-actions>list of pending interface actions</a>
   that run the following steps:</p>

Modified: index
===================================================================
--- index	2013-10-15 23:19:20 UTC (rev 8226)
+++ index	2013-10-16 22:43:22 UTC (rev 8227)
@@ -256,7 +256,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 15 October 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 16 October 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -37232,7 +37232,16 @@
 
    <li><p>Return <var title="">result</var>.</li>
 
-  </ol><p>The <dfn id=dom-context-2d-scrollpathintoview title=dom-context-2d-scrollPathIntoView><code>scrollPathIntoView()</code></dfn>
+  </ol><p>User agents should not implicitly close open subpaths in the intended path when drawing the
+  focus ring.</p>
+
+  <p class=note>This might be a moot point, however. For example, if the focus ring is drawn as an
+  axis-aligned bounding rectangle around the points in the intended path, then whether the subpaths
+  are closed or not has no effect. This specification intentionally does not specify precisely how
+  focus rings are to be drawn: user agents are expected to honor their platform's native
+  conventions.</p>
+
+  <hr><p>The <dfn id=dom-context-2d-scrollpathintoview title=dom-context-2d-scrollPathIntoView><code>scrollPathIntoView()</code></dfn>
   method, when invoked, if the <code><a href=#canvasrenderingcontext2d>CanvasRenderingContext2D</a></code> object's <a href=#concept-canvas-context-bitmap-mode title=concept-canvas-context-bitmap-mode>context bitmap mode</a> is <a href=#concept-canvas-fixed title=concept-canvas-fixed>fixed</a>, must run the following steps; and otherwise, must add
   instructions to the <a href=#scratch-bitmap>scratch bitmap</a>'s <a href=#list-of-pending-interface-actions>list of pending interface actions</a>
   that run the following steps:</p>

Modified: source
===================================================================
--- source	2013-10-15 23:19:20 UTC (rev 8226)
+++ source	2013-10-16 22:43:22 UTC (rev 8227)
@@ -40607,6 +40607,17 @@
 
   </ol>
 
+  <p>User agents should not implicitly close open subpaths in the intended path when drawing the
+  focus ring.</p>
+
+  <p class="note">This might be a moot point, however. For example, if the focus ring is drawn as an
+  axis-aligned bounding rectangle around the points in the intended path, then whether the subpaths
+  are closed or not has no effect. This specification intentionally does not specify precisely how
+  focus rings are to be drawn: user agents are expected to honor their platform's native
+  conventions.</p>
+
+  <hr>
+
   <p>The <dfn title="dom-context-2d-scrollPathIntoView"><code>scrollPathIntoView()</code></dfn>
   method, when invoked, if the <code>CanvasRenderingContext2D</code> object's <span
   title="concept-canvas-context-bitmap-mode">context bitmap mode</span> is <span




More information about the Commit-Watchers mailing list