[html5] r7458 - [giow] (2) Make UA-provided focusable controls that are part of other elements b [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2012-10-12 11:03:12 -0700 (Fri, 12 Oct 2012)
New Revision: 7458

Modified:
   complete.html
   index
   source
Log:
[giow] (2) Make UA-provided focusable controls that are part of other elements be focusable.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17554
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2012-10-12 17:36:52 UTC (rev 7457)
+++ complete.html	2012-10-12 18:03:12 UTC (rev 7458)
@@ -114,7 +114,6 @@
 
    .applies thead th > * { display: block; }
    .applies thead code { display: block; }
-   .applies tbody th { whitespace: nowrap; }
    .applies td { text-align: center; }
    .applies .yes { background: yellow; }
 
@@ -78344,11 +78343,13 @@
    <li><a href=#browsing-context-container title="browsing context container">Browsing context
    containers</a></li> <!-- like <iframe>s -->
 
-  </ul><p>In addition, each shape that is generated for an
-  <code><a href=#the-area-element>area</a></code> element should be <a href=#focusable>focusable</a>, unless
-  platform conventions dictate otherwise. (A single <code><a href=#the-area-element>area</a></code>
-  element can correspond to multiple shapes, since image maps can be
-  reused with multiple images on a page.)</p>
+  </ul><p>In addition, each shape that is generated for an <code><a href=#the-area-element>area</a></code> element, any
+  user-agent-provided interface components of <span title="media elements">media elements</span>
+  (e.g. a play button), and distinct user interface components of form controls (e.g. "up" and
+  "down" buttons on an <code title=attr-input-type-number><a href="#number-state-(type=number)"><input type=number></a></code> spin
+  control), should be <a href=#focusable>focusable</a>, unless platform conventions dictate otherwise. (A
+  single <code><a href=#the-area-element>area</a></code> element can correspond to multiple shapes, since image maps can be reused
+  with multiple images on a page.)</p>
 
   <p>The user agent may also make part of a <code><a href=#the-details-element>details</a></code>
   element's rendering <a href=#focusable>focusable</a>, to enable the element to

Modified: index
===================================================================
--- index	2012-10-12 17:36:52 UTC (rev 7457)
+++ index	2012-10-12 18:03:12 UTC (rev 7458)
@@ -114,7 +114,6 @@
 
    .applies thead th > * { display: block; }
    .applies thead code { display: block; }
-   .applies tbody th { whitespace: nowrap; }
    .applies td { text-align: center; }
    .applies .yes { background: yellow; }
 
@@ -78344,11 +78343,13 @@
    <li><a href=#browsing-context-container title="browsing context container">Browsing context
    containers</a></li> <!-- like <iframe>s -->
 
-  </ul><p>In addition, each shape that is generated for an
-  <code><a href=#the-area-element>area</a></code> element should be <a href=#focusable>focusable</a>, unless
-  platform conventions dictate otherwise. (A single <code><a href=#the-area-element>area</a></code>
-  element can correspond to multiple shapes, since image maps can be
-  reused with multiple images on a page.)</p>
+  </ul><p>In addition, each shape that is generated for an <code><a href=#the-area-element>area</a></code> element, any
+  user-agent-provided interface components of <span title="media elements">media elements</span>
+  (e.g. a play button), and distinct user interface components of form controls (e.g. "up" and
+  "down" buttons on an <code title=attr-input-type-number><a href="#number-state-(type=number)"><input type=number></a></code> spin
+  control), should be <a href=#focusable>focusable</a>, unless platform conventions dictate otherwise. (A
+  single <code><a href=#the-area-element>area</a></code> element can correspond to multiple shapes, since image maps can be reused
+  with multiple images on a page.)</p>
 
   <p>The user agent may also make part of a <code><a href=#the-details-element>details</a></code>
   element's rendering <a href=#focusable>focusable</a>, to enable the element to

Modified: source
===================================================================
--- source	2012-10-12 17:36:52 UTC (rev 7457)
+++ source	2012-10-12 18:03:12 UTC (rev 7458)
@@ -91653,11 +91653,13 @@
 
   </ul>
 
-  <p>In addition, each shape that is generated for an
-  <code>area</code> element should be <span>focusable</span>, unless
-  platform conventions dictate otherwise. (A single <code>area</code>
-  element can correspond to multiple shapes, since image maps can be
-  reused with multiple images on a page.)</p>
+  <p>In addition, each shape that is generated for an <code>area</code> element, any
+  user-agent-provided interface components of <span title="media elements">media elements</span>
+  (e.g. a play button), and distinct user interface components of form controls (e.g. "up" and
+  "down" buttons on an <code title="attr-input-type-number"><input type=number></code> spin
+  control), should be <span>focusable</span>, unless platform conventions dictate otherwise. (A
+  single <code>area</code> element can correspond to multiple shapes, since image maps can be reused
+  with multiple images on a page.)</p>
 
   <p>The user agent may also make part of a <code>details</code>
   element's rendering <span>focusable</span>, to enable the element to