Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[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

git-svn-id: http://svn.whatwg.org/webapps@7458 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 12, 2012
1 parent 0ec3a8d commit 902d12e
Show file tree
Hide file tree
Showing 3 changed files with 21 additions and 17 deletions.
13 changes: 7 additions & 6 deletions complete.html
Expand Up @@ -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; }

Expand Down Expand Up @@ -78344,11 +78343,13 @@ <h4 id=focus-management><span class=secno>8.4.2 </span>Focus management</h4>
<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)">&lt;input type=number&gt;</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
Expand Down
13 changes: 7 additions & 6 deletions index
Expand Up @@ -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; }

Expand Down Expand Up @@ -78344,11 +78343,13 @@ interface <dfn id=navigatorstorageutils>NavigatorStorageUtils</dfn> {
<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)">&lt;input type=number&gt;</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
Expand Down
12 changes: 7 additions & 5 deletions source
Expand Up @@ -91653,11 +91653,13 @@ interface <dfn>NavigatorStorageUtils</dfn> {

</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">&lt;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
Expand Down

0 comments on commit 902d12e

Please sign in to comment.