- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Aug 2011 03:47:19 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv10329 Modified Files: Overview.html Log Message: Make sure commands aren't exposed when not in a document. (whatwg r6480) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.5181 retrieving revision 1.5182 diff -u -d -r1.5181 -r1.5182 --- Overview.html 17 Aug 2011 00:43:14 -0000 1.5181 +++ Overview.html 17 Aug 2011 03:47:15 -0000 1.5182 @@ -41266,8 +41266,10 @@ node, whose filter matches only elements that <a href="#concept-command" title="concept-command">define commands</a> and have <a href="#command-facet-id" title="command-facet-ID">IDs</a>.</p> </div><hr><p>User agents may expose the <a href="#concept-command" title="concept-command">commands</a> whose <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a> facet is false - (visible), e.g. in the user agent's menu bar. User agents are - encouraged to do this especially for commands that have <a href="#command-facet-accesskey" title="command-facet-AccessKey">Access Keys</a>, as a way to + (visible) and whose elements are <a href="#in-a-document">in a + <code>Document</code></a>. For example, such commands could be + listed in the user agent's menu bar. User agents are encouraged to + do this especially for commands that have <a href="#command-facet-accesskey" title="command-facet-AccessKey">Access Keys</a>, as a way to advertise those keys to the user.<div class="impl"> <h5 id="using-the-a-element-to-define-a-command"><span class="secno">4.11.5.1 </span><dfn title="a-command">Using the <code>a</code> element to define a command</dfn></h5> @@ -52347,16 +52349,17 @@ <p>When the user presses the key combination corresponding to the <a href="#assigned-access-key">assigned access key</a> for an element, if the element - <a href="#concept-command" title="concept-command">defines a command</a>, and the + <a href="#concept-command" title="concept-command">defines a command</a>, the command's <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden - State</a> facet is false (visible), and the command's <a href="#command-facet-disabledstate" title="command-facet-DisabledState">Disabled State</a> facet is - also false (enabled), then the user agent must trigger the <a href="#command-facet-action" title="command-facet-Action">Action</a> of the command.</p> + State</a> facet is false (visible), the command's <a href="#command-facet-disabledstate" title="command-facet-DisabledState">Disabled State</a> facet is + also false (enabled), and the element is <a href="#in-a-document">in a + <code>Document</code></a>, then the user agent must trigger the + <a href="#command-facet-action" title="command-facet-Action">Action</a> of the command.</p> - <p>User agents may expose elements that have an <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> attribute in other ways as + <p class="note">User agents might expose elements that have an <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> attribute in other ways as well, e.g. in a menu displayed in response to a specific key - combination.</p> - - <p>The <dfn id="dom-accesskey" title="dom-accessKey"><code>accessKey</code></dfn> IDL + combination.</p> + <hr><p>The <dfn id="dom-accesskey" title="dom-accessKey"><code>accessKey</code></dfn> IDL attribute must <a href="#reflect">reflect</a> the <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> content attribute.</p> <p>The <dfn id="dom-accesskeylabel" title="dom-accessKeyLabel"><code>accessKeyLabel</code></dfn> IDL
Received on Wednesday, 17 August 2011 03:47:21 UTC