[html5] r8414 - [e] (0) Change a non-normative confusing note to a normative less confusing (hop [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 21 15:34:03 PST 2014
Author: ianh
Date: 2014-01-21 15:34:02 -0800 (Tue, 21 Jan 2014)
New Revision: 8414
Modified:
complete.html
index
source
Log:
[e] (0) Change a non-normative confusing note to a normative less confusing (hopefully) description, in the canvas section on focus rings
Affected topics: Canvas, HTML
Modified: complete.html
===================================================================
--- complete.html 2014-01-21 22:53:00 UTC (rev 8413)
+++ complete.html 2014-01-21 23:34:02 UTC (rev 8414)
@@ -57642,14 +57642,13 @@
until the next time the <a href=#event-loop>event loop</a> reaches its "update the rendering" step to
optionally inform the user.</li>
- </ol><p class=note id=inform>"Inform the user", as used in this section, could mean calling a
- system accessibility API, which would notify assistive technologies such as magnification tools.
- To properly drive magnification based on a focus change, a system accessibility API driving a
- screen magnifier needs the bounds for the newly focused object. The methods above are intended to
- enable this by allowing the user agent to report the bounding box of the path used to render the
- focus ring as the bounds of the <var title="">element</var> element passed as an argument, if that
- element is focused, and the bounding box of the area to which the user agent is scrolling as the
- bounding box of the current selection.</p>
+ </ol><p id=inform>"Inform the user", as used in this section, does not imply any persistent state
+ change. It could mean, for instance, calling a system accessibility API to notify assistive
+ technologies such as magnification tools so that the user's magnifier moves to the given area of
+ the canvas. However, it does not associate the path with the element, or provide a region for
+ tactile feedback, etc. To persistently associate a region with information provided to
+ accessibility tools, use the <code title=dom-context-2d-addHitRegion><a href=#dom-context-2d-addhitregion>addHitRegion()</a></code>
+ API.</p>
<hr><p>The <dfn id=dom-context-2d-clip title=dom-context-2d-clip><code>clip()</code></dfn> method must create a new
<dfn id=clipping-region>clipping region</dfn> by calculating the intersection of the current clipping region and the
@@ -102907,6 +102906,7 @@
Tommy Thorsen,
Tony Ross,
Travis Leithead,
+ Trevor Saunders,
Tyler Close,
Victor Carbune,
Vipul Snehadeep Chawathe,
Modified: index
===================================================================
--- index 2014-01-21 22:53:00 UTC (rev 8413)
+++ index 2014-01-21 23:34:02 UTC (rev 8414)
@@ -57642,14 +57642,13 @@
until the next time the <a href=#event-loop>event loop</a> reaches its "update the rendering" step to
optionally inform the user.</li>
- </ol><p class=note id=inform>"Inform the user", as used in this section, could mean calling a
- system accessibility API, which would notify assistive technologies such as magnification tools.
- To properly drive magnification based on a focus change, a system accessibility API driving a
- screen magnifier needs the bounds for the newly focused object. The methods above are intended to
- enable this by allowing the user agent to report the bounding box of the path used to render the
- focus ring as the bounds of the <var title="">element</var> element passed as an argument, if that
- element is focused, and the bounding box of the area to which the user agent is scrolling as the
- bounding box of the current selection.</p>
+ </ol><p id=inform>"Inform the user", as used in this section, does not imply any persistent state
+ change. It could mean, for instance, calling a system accessibility API to notify assistive
+ technologies such as magnification tools so that the user's magnifier moves to the given area of
+ the canvas. However, it does not associate the path with the element, or provide a region for
+ tactile feedback, etc. To persistently associate a region with information provided to
+ accessibility tools, use the <code title=dom-context-2d-addHitRegion><a href=#dom-context-2d-addhitregion>addHitRegion()</a></code>
+ API.</p>
<hr><p>The <dfn id=dom-context-2d-clip title=dom-context-2d-clip><code>clip()</code></dfn> method must create a new
<dfn id=clipping-region>clipping region</dfn> by calculating the intersection of the current clipping region and the
@@ -102907,6 +102906,7 @@
Tommy Thorsen,
Tony Ross,
Travis Leithead,
+ Trevor Saunders,
Tyler Close,
Victor Carbune,
Vipul Snehadeep Chawathe,
Modified: source
===================================================================
--- source 2014-01-21 22:53:00 UTC (rev 8413)
+++ source 2014-01-21 23:34:02 UTC (rev 8414)
@@ -64091,14 +64091,13 @@
</ol>
- <p class="note" id="inform">"Inform the user", as used in this section, could mean calling a
- system accessibility API, which would notify assistive technologies such as magnification tools.
- To properly drive magnification based on a focus change, a system accessibility API driving a
- screen magnifier needs the bounds for the newly focused object. The methods above are intended to
- enable this by allowing the user agent to report the bounding box of the path used to render the
- focus ring as the bounds of the <var data-x="">element</var> element passed as an argument, if that
- element is focused, and the bounding box of the area to which the user agent is scrolling as the
- bounding box of the current selection.</p>
+ <p id="inform">"Inform the user", as used in this section, does not imply any persistent state
+ change. It could mean, for instance, calling a system accessibility API to notify assistive
+ technologies such as magnification tools so that the user's magnifier moves to the given area of
+ the canvas. However, it does not associate the path with the element, or provide a region for
+ tactile feedback, etc. To persistently associate a region with information provided to
+ accessibility tools, use the <code data-x="dom-context-2d-addHitRegion">addHitRegion()</code>
+ API.</p>
<hr>
@@ -114898,6 +114897,7 @@
Tommy Thorsen,
Tony Ross,
Travis Leithead,
+ Trevor Saunders,
Tyler Close,
Victor Carbune,
Vipul Snehadeep Chawathe,
More information about the Commit-Watchers
mailing list