W3C home > Mailing lists > Public > public-html-commits@w3.org > May 2009

html5/spec Overview.html,1.2223,1.2224

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 03 May 2009 01:55:17 +0000
To: public-html-commits@w3.org
Message-Id: <E1M0QvG-0000Uw-3G@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv1900

Modified Files:
	Overview.html 
Log Message:
Define accesskey='' and related magic to try to Solve the Problem. (whatwg r3065)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2223
retrieving revision 1.2224
diff -u -d -r1.2223 -r1.2224
--- Overview.html	2 May 2009 21:34:14 -0000	1.2223
+++ Overview.html	3 May 2009 01:55:14 -0000	1.2224
@@ -148,7 +148,7 @@
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
    <!--ZZZ:-->
    <!--<h2 class="no-num no-toc">W3C Working Draft 23 April 2009</h2>-->
-   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 2 May 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 3 May 2009</h2>
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out
     <dt>This Version:</dt>
@@ -241,7 +241,7 @@
   track.
   <!--ZZZ:-->
   <!--This specification is the 23 April 2009 Working Draft.-->
-  This specification is the 2 May 2009 Editor's Draft.
+  This specification is the 3 May 2009 Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href="http://www.whatwg.org/">WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -713,7 +713,8 @@
        <li><a href="#using-the-option-element-to-define-a-command"><span class="secno">4.11.6.4 </span>Using the <code>option</code> element to define a command</a></li>
        <li><a href="#using-the-command-element-to-define-a-command"><span class="secno">4.11.6.5 </span>Using the <code>command</code> element to define
   a command</a></li>
-       <li><a href="#using-the-bb-element-to-define-a-command"><span class="secno">4.11.6.6 </span>Using the <code>bb</code> element to define a command</a></ol></ol></li>
+       <li><a href="#using-the-bb-element-to-define-a-command"><span class="secno">4.11.6.6 </span>Using the <code>bb</code> element to define a command</a></li>
+       <li><a href="#using-the-accesskey-attribute-to-define-a-command"><span class="secno">4.11.6.7 </span>Using the <code title="attr-accesskey">accesskey</code> attribute to define a command</a></ol></ol></li>
    <li><a href="#miscellaneous-elements"><span class="secno">4.12 </span>Miscellaneous elements</a>
     <ol>
      <li><a href="#the-legend-element"><span class="secno">4.12.1 </span>The <code>legend</code> element</a></li>
@@ -867,44 +868,45 @@
      <li><a href="#focus-management"><span class="secno">6.5.2 </span>Focus management</a></li>
      <li><a href="#document-level-focus-apis"><span class="secno">6.5.3 </span>Document-level focus APIs</a></li>
      <li><a href="#element-level-focus-apis"><span class="secno">6.5.4 </span>Element-level focus APIs</a></ol></li>
-   <li><a href="#selection"><span class="secno">6.6 </span>The text selection APIs</a>
+   <li><a href="#the-accesskey-attribute"><span class="secno">6.6 </span>The <code>accesskey</code> attribute</a></li>
+   <li><a href="#selection"><span class="secno">6.7 </span>The text selection APIs</a>
     <ol>
-     <li><a href="#documentSelection"><span class="secno">6.6.1 </span>APIs for the browsing context selection</a></li>
-     <li><a href="#textFieldSelection"><span class="secno">6.6.2 </span>APIs for the text field selections</a></ol></li>
-   <li><a href="#contenteditable"><span class="secno">6.7 </span>The <code title="attr-contenteditable">contenteditable</code> attribute</a>
+     <li><a href="#documentSelection"><span class="secno">6.7.1 </span>APIs for the browsing context selection</a></li>
+     <li><a href="#textFieldSelection"><span class="secno">6.7.2 </span>APIs for the text field selections</a></ol></li>
+   <li><a href="#contenteditable"><span class="secno">6.8 </span>The <code title="attr-contenteditable">contenteditable</code> attribute</a>
     <ol>
-     <li><a href="#user-editing-actions"><span class="secno">6.7.1 </span>User editing actions</a></li>
-     <li><a href="#making-entire-documents-editable"><span class="secno">6.7.2 </span>Making entire documents editable</a></ol></li>
-   <li><a href="#spelling-and-grammar-checking"><span class="secno">6.8 </span>Spelling and grammar checking</a></li>
-   <li><a href="#dnd"><span class="secno">6.9 </span>Drag and drop</a>
+     <li><a href="#user-editing-actions"><span class="secno">6.8.1 </span>User editing actions</a></li>
+     <li><a href="#making-entire-documents-editable"><span class="secno">6.8.2 </span>Making entire documents editable</a></ol></li>
+   <li><a href="#spelling-and-grammar-checking"><span class="secno">6.9 </span>Spelling and grammar checking</a></li>
+   <li><a href="#dnd"><span class="secno">6.10 </span>Drag and drop</a>
     <ol>
-     <li><a href="#introduction-4"><span class="secno">6.9.1 </span>Introduction</a></li>
-     <li><a href="#the-dragevent-and-datatransfer-interfaces"><span class="secno">6.9.2 </span>The <code>DragEvent</code> and <code>DataTransfer</code> interfaces</a></li>
-     <li><a href="#events-fired-during-a-drag-and-drop-action"><span class="secno">6.9.3 </span>Events fired during a drag-and-drop action</a></li>
-     <li><a href="#drag-and-drop-processing-model"><span class="secno">6.9.4 </span>Drag-and-drop processing model</a>
+     <li><a href="#introduction-4"><span class="secno">6.10.1 </span>Introduction</a></li>
+     <li><a href="#the-dragevent-and-datatransfer-interfaces"><span class="secno">6.10.2 </span>The <code>DragEvent</code> and <code>DataTransfer</code> interfaces</a></li>
+     <li><a href="#events-fired-during-a-drag-and-drop-action"><span class="secno">6.10.3 </span>Events fired during a drag-and-drop action</a></li>
+     <li><a href="#drag-and-drop-processing-model"><span class="secno">6.10.4 </span>Drag-and-drop processing model</a>
       <ol>
-       <li><a href="#when-the-drag-and-drop-operation-starts-or-ends-in-another-document"><span class="secno">6.9.4.1 </span>When the drag-and-drop operation starts or ends in another
+       <li><a href="#when-the-drag-and-drop-operation-starts-or-ends-in-another-document"><span class="secno">6.10.4.1 </span>When the drag-and-drop operation starts or ends in another
   document</a></li>
-       <li><a href="#when-the-drag-and-drop-operation-starts-or-ends-in-another-application"><span class="secno">6.9.4.2 </span>When the drag-and-drop operation starts or ends in another
+       <li><a href="#when-the-drag-and-drop-operation-starts-or-ends-in-another-application"><span class="secno">6.10.4.2 </span>When the drag-and-drop operation starts or ends in another
   application</a></ol></li>
-     <li><a href="#the-draggable-attribute"><span class="secno">6.9.5 </span>The <code>draggable</code> attribute</a></li>
-     <li><a href="#copy-and-paste"><span class="secno">6.9.6 </span>Copy and paste</a>
+     <li><a href="#the-draggable-attribute"><span class="secno">6.10.5 </span>The <code>draggable</code> attribute</a></li>
+     <li><a href="#copy-and-paste"><span class="secno">6.10.6 </span>Copy and paste</a>
       <ol>
-       <li><a href="#copy-to-clipboard"><span class="secno">6.9.6.1 </span>Copy to clipboard</a></li>
-       <li><a href="#cut-to-clipboard"><span class="secno">6.9.6.2 </span>Cut to clipboard</a></li>
-       <li><a href="#paste-from-clipboard"><span class="secno">6.9.6.3 </span>Paste from clipboard</a></li>
-       <li><a href="#paste-from-selection"><span class="secno">6.9.6.4 </span>Paste from selection</a></ol></li>
-     <li><a href="#security-risks-in-the-drag-and-drop-model"><span class="secno">6.9.7 </span>Security risks in the drag-and-drop model</a></ol></li>
-   <li><a href="#undo"><span class="secno">6.10 </span>Undo history</a>
+       <li><a href="#copy-to-clipboard"><span class="secno">6.10.6.1 </span>Copy to clipboard</a></li>
+       <li><a href="#cut-to-clipboard"><span class="secno">6.10.6.2 </span>Cut to clipboard</a></li>
+       <li><a href="#paste-from-clipboard"><span class="secno">6.10.6.3 </span>Paste from clipboard</a></li>
+       <li><a href="#paste-from-selection"><span class="secno">6.10.6.4 </span>Paste from selection</a></ol></li>
+     <li><a href="#security-risks-in-the-drag-and-drop-model"><span class="secno">6.10.7 </span>Security risks in the drag-and-drop model</a></ol></li>
+   <li><a href="#undo"><span class="secno">6.11 </span>Undo history</a>
     <ol>
-     <li><a href="#introduction-5"><span class="secno">6.10.1 </span>Introduction</a></li>
-     <li><a href="#definitions-2"><span class="secno">6.10.2 </span>Definitions</a></li>
-     <li><a href="#the-undomanager-interface"><span class="secno">6.10.3 </span>The <code>UndoManager</code> interface</a></li>
-     <li><a href="#undo:-moving-back-in-the-undo-transaction-history"><span class="secno">6.10.4 </span>Undo: moving back in the undo transaction history</a></li>
-     <li><a href="#redo:-moving-forward-in-the-undo-transaction-history"><span class="secno">6.10.5 </span>Redo: moving forward in the undo transaction history</a></li>
-     <li><a href="#the-undomanagerevent-interface-and-the-undo-and-redo-events"><span class="secno">6.10.6 </span>The <code>UndoManagerEvent</code> interface and the <code title="event-undo">undo</code> and <code title="event-redo">redo</code> events</a></li>
-     <li><a href="#implementation-notes"><span class="secno">6.10.7 </span>Implementation notes</a></ol></li>
-   <li><a href="#editing-apis"><span class="secno">6.11 </span>Editing APIs</a></ol></li>
+     <li><a href="#introduction-5"><span class="secno">6.11.1 </span>Introduction</a></li>
+     <li><a href="#definitions-2"><span class="secno">6.11.2 </span>Definitions</a></li>
+     <li><a href="#the-undomanager-interface"><span class="secno">6.11.3 </span>The <code>UndoManager</code> interface</a></li>
+     <li><a href="#undo:-moving-back-in-the-undo-transaction-history"><span class="secno">6.11.4 </span>Undo: moving back in the undo transaction history</a></li>
+     <li><a href="#redo:-moving-forward-in-the-undo-transaction-history"><span class="secno">6.11.5 </span>Redo: moving forward in the undo transaction history</a></li>
+     <li><a href="#the-undomanagerevent-interface-and-the-undo-and-redo-events"><span class="secno">6.11.6 </span>The <code>UndoManagerEvent</code> interface and the <code title="event-undo">undo</code> and <code title="event-redo">redo</code> events</a></li>
+     <li><a href="#implementation-notes"><span class="secno">6.11.7 </span>Implementation notes</a></ol></li>
+   <li><a href="#editing-apis"><span class="secno">6.12 </span>Editing APIs</a></ol></li>
  <li><a href="#comms"><span class="secno">7 </span>Communication</a>
   <ol>
    <li><a href="#event-definitions"><span class="secno">7.1 </span>Event definitions</a></li>
@@ -7087,6 +7089,8 @@
            attribute long <a href="#dom-tabindex" title="dom-tabindex">tabIndex</a>;
   void <a href="#dom-focus" title="dom-focus">focus</a>();
   void <a href="#dom-blur" title="dom-blur">blur</a>();
+           attribute DOMString <a href="#dom-accesskey" title="dom-accessKey">accessKey</a>;
+  readonly attribute DOMString <a href="#dom-accesskeylabel" title="dom-accessKeyLabel">accessKeyLabel</a>;
            attribute boolean <a href="#dom-draggable" title="dom-draggable">draggable</a>;
            attribute DOMString <a href="#dom-contenteditable" title="dom-contentEditable">contentEditable</a>;
   readonly attribute boolean <a href="#dom-iscontenteditable" title="dom-isContentEditable">isContentEditable</a>;
@@ -7165,7 +7169,8 @@
   members of this interface are therefore described in various
   different sections of this specification.<h4 id="global-attributes"><span class="secno">3.3.3 </span><dfn>Global attributes</dfn></h4><p>The following attributes are common to and may be specified on
   all <a href="#html-elements">HTML elements</a><span class="impl"> (even those not
-  defined in this specification)</span>:<ul class="brief"><li><code title="attr-class"><a href="#classes">class</a></code></li>
+  defined in this specification)</span>:<ul class="brief"><li><code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code></li>
+   <li><code title="attr-class"><a href="#classes">class</a></code></li>
    <li><code title="attr-contenteditable"><a href="#attr-contenteditable">contenteditable</a></code></li>
    <li><code title="attr-contextmenu"><a href="#attr-contextmenu">contextmenu</a></code></li>
    <li><code title="attr-dir"><a href="#the-dir-attribute">dir</a></code></li>
@@ -35076,6 +35081,11 @@
    represents the action. A command might not have an Icon.</dd> <!--
    changing base URLs might change the icon -->
 
+   <dt><dfn id="command-facet-accesskey" title="command-facet-AccessKey">Access Key</dfn></dt>
+
+   <dd>A key combination selected by the user agent that triggers the
+   command. A command might not have an Access Key.</dd>
+
    <dt><dfn id="command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</dfn></dt>
 
    <dd>Whether the command is hidden or not (basically, whether it
@@ -35146,6 +35156,14 @@
 
    </dd>
 
+   <dt><var title="">element</var> . <code title="dom-accessKeyLabel"><a href="#dom-accesskeylabel">accessKeyLabel</a></code></dt>
+
+   <dd>
+
+    <p>Exposes the <a href="#command-facet-accesskey" title="command-facet-AccessKey">Access Key</a> facet of the command.</p>
+
+   </dd>
+
    <dt><var title="">element</var> . <code title="dom-hidden"><a href="#dom-hidden">hidden</a></code></dt>
 
    <dd>
@@ -35238,10 +35256,10 @@
   <p class="note">The <a href="#command-facet-id" title="command-facet-ID">ID</a> facet
   is exposed by the the <code title="dom-id"><a href="#dom-id">id</a></code> DOM attribute,
   the <a href="#command-facet-hint" title="command-facet-Hint">Hint</a> facet is exposed by
-  the <code title="dom-title"><a href="#dom-title">title</a></code> DOM attribute, and the
-  <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a> facet is
-  exposed by the <code title="dom-hidden"><a href="#dom-hidden">hidden</a></code> DOM
-  attribute.</p>
+  the <code title="dom-title"><a href="#dom-title">title</a></code> DOM attribute, the <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> facet is exposed by
+  the <code title="dom-accessKeyLabel"><a href="#dom-accesskeylabel">accessKeyLabel</a></code> DOM
+  attribute, and the <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden
+  State</a> facet is exposed by the <code title="dom-hidden"><a href="#dom-hidden">hidden</a></code> DOM attribute.</p>
 
   </div><hr><dl class="domintro"><dt><var title="">document</var> . <code title="dom-document-commands"><a href="#dom-document-commands">commands</a></code></dt>
    <dd>
@@ -35256,7 +35274,10 @@
   <code><a href="#htmlcollection-0">HTMLCollection</a></code> rooted at the <code>Document</code>
   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><div class="impl">
+  </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
+  advertise those keys to the user.<div class="impl">
 
   <h5 id="using-the-a-element-to-define-a-command"><span class="secno">4.11.6.1 </span><dfn title="a-command">Using the <code>a</code> element to define a command</dfn></h5>
 
@@ -35285,6 +35306,10 @@
   element, if there is such an element and resolving its attribute is
   successful. Otherwise, there is no <a href="#command-facet-icon" title="command-facet-Icon">Icon</a> for the command.</p>
 
+  <p>The <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> of the
+  command is the element's <a href="#assigned-access-key">assigned access key</a>, if
+  any.</p>
+
   <p>The <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>
   of the command is true (hidden) if the element has a <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute, and false
   otherwise.</p>
@@ -35304,7 +35329,7 @@
 
   <p>A <code><a href="#the-button-element">button</a></code> element always <a href="#concept-command" title="concept-command">defines a command</a>.</p>
 
-  <p>The <a href="#command-facet-type" title="command-facet-Type">Type</a>, <a href="#command-facet-id" title="command-facet-ID">ID</a>, <a href="#command-facet-label" title="command-facet-Label">Label</a>, <a href="#command-facet-hint" title="command-facet-Hint">Hint</a>, <a href="#command-facet-icon" title="command-facet-Icon">Icon</a>, <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>, <a href="#command-facet-checkedstate" title="command-facet-CheckedState">Checked State</a>, and <a href="#command-facet-action" title="command-facet-Action">Action</a> facets of the command are
+  <p>The <a href="#command-facet-type" title="command-facet-Type">Type</a>, <a href="#command-facet-id" title="command-facet-ID">ID</a>, <a href="#command-facet-label" title="command-facet-Label">Label</a>, <a href="#command-facet-hint" title="command-facet-Hint">Hint</a>, <a href="#command-facet-icon" title="command-facet-Icon">Icon</a>, <a href="#command-facet-accesskey" title="command-facet-AccessKey">Access Key</a>, <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>, <a href="#command-facet-checkedstate" title="command-facet-CheckedState">Checked State</a>, and <a href="#command-facet-action" title="command-facet-Action">Action</a> facets of the command are
   determined <a href="#using-the-a-element-to-define-a-command" title="a-command">as for <code>a</code>
   elements</a> (see the previous section).</p>
 
@@ -35339,7 +35364,7 @@
   "radio" or "checkbox". If the element is a <a href="#labeled-control">labeled
   control</a>, the <code><a href="#textcontent">textContent</a></code> of the first
   <code><a href="#the-label-element">label</a></code> element in <a href="#tree-order">tree order</a> whose
-  <a href="#labeled-control">labeled control</a> is the element in question is the <a href="#command-facet-label" title="command-facet-Label">Label</a> (in DOM terms, this the
+  <a href="#labeled-control">labeled control</a> is the element in question is the <a href="#command-facet-label" title="command-facet-Label">Label</a> (in DOM terms, this is the
   string given by <code><var title="">element</var>.labels[0].textContent</code>).  Otherwise,
   the value of the <code title="attr-input-value"><a href="#attr-input-value">value</a></code>
   attribute, if present, is the <a href="#command-facet-label" title="command-facet-Label">Label</a>. Otherwise, the <a href="#command-facet-label" title="command-facet-Label">Label</a> is the empty string.</p>
@@ -35353,6 +35378,10 @@
   <p>There is no <a href="#command-facet-icon" title="command-facet-Icon">Icon</a> for the
   command.</p>
 
+  <p>The <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> of the
+  command is the element's <a href="#assigned-access-key">assigned access key</a>, if
+  any.</p>
+
   <p>The <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>
   of the command is true (hidden) if the element has a <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute, and false
   otherwise.</p>
@@ -35401,6 +35430,10 @@
   <p>There is no <a href="#command-facet-icon" title="command-facet-Icon">Icon</a> for the
   command.</p>
 
+  <p>The <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> of the
+  command is the element's <a href="#assigned-access-key">assigned access key</a>, if
+  any.</p>
+
   <p>The <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>
   of the command is true (hidden) if the element has a <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute, and false
   otherwise.</p>
@@ -35450,6 +35483,10 @@
   element, if it has such an attribute and resolving it is
   successful. Otherwise, there is no <a href="#command-facet-icon" title="command-facet-Icon">Icon</a> for the command.</p>
 
+  <p>The <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> of the
+  command is the element's <a href="#assigned-access-key">assigned access key</a>, if
+  any.</p>
+
   <p>The <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>
   of the command is true (hidden) if the element has a <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute, and false
   otherwise.</p>
@@ -35500,6 +35537,10 @@
   successful. Otherwise, the <a href="#command-facet-icon" title="command-facet-Icon">Icon</a> is a user-agent-defined image
   appropriate for the <code><a href="#the-bb-element">bb</a></code> element's <code title="attr-bb-type"><a href="#attr-bb-type">type</a></code> attribute's state.</p>
 
+  <p>The <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> of the
+  command is the element's <a href="#assigned-access-key">assigned access key</a>, if
+  any.</p>
+
   <p>The <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>
   facet of the command is true (hidden) if the <code><a href="#the-bb-element">bb</a></code>
   element's <code title="attr-bb-type"><a href="#attr-bb-type">type</a></code> attribute's state
@@ -35520,6 +35561,62 @@
   element's <code title="attr-bb-type"><a href="#attr-bb-type">type</a></code> attribute's
   state.</p>
 
+
+  <h5 id="using-the-accesskey-attribute-to-define-a-command"><span class="secno">4.11.6.7 </span><dfn title="accesskey-command">Using the <code title="attr-accesskey">accesskey</code> attribute to define a command</dfn></h5>
+
+  <p>An element that is <a href="#focusable">focusable</a>, has an <a href="#assigned-access-key">assigned
+  access key</a>, and is neither an <code><a href="#the-a-element">a</a></code> element with an
+  <code title="attr-a-href">href</code> attribute, a
+  <code><a href="#the-button-element">button</a></code> element, an <code><a href="#the-input-element">input</a></code> element whose
+  attribute is in one of the <a href="#submit-button-state" title="attr-input-type-submit">Submit Button</a>, <a href="#reset-button-state" title="attr-input-type-reset">Reset Button</a>, <a href="#button-state" title="attr-input-type-button">Button</a>, <a href="#radio-button-state" title="attr-input-type-radio">Radio Button</a>, or <a href="#checkbox-state" title="attr-input-type-checkbox">Checkbox</a> states, an
+  <code><a href="#the-option-element">option</a></code> element with an ancestor <code><a href="#the-select-element">select</a></code>
+  element and either no <code title="attr-option-value"><a href="#attr-option-value">value</a></code>
+  attribute or a <code title="attr-option-value"><a href="#attr-option-value">value</a></code>
+  attribute that is not the empty string, a <code><a href="#the-command">command</a></code>
+  element, nor a <code><a href="#the-bb-element">bb</a></code> element, <a href="#concept-command" title="concept-command">defines a command</a>.</p>
+
+  <p>The <a href="#command-facet-type" title="command-facet-Type">Type</a> of the command
+  is "command".</p>
+
+  <p>The <a href="#command-facet-id" title="command-facet-ID">ID</a> of the command is
+  the value of the <code title="attr-id"><a href="#the-id-attribute">id</a></code> attribute of the
+  element, if the attribute is present and not empty. Otherwise the
+  command is an <a href="#anonymous-command">anonymous command</a>.</p>
+
+  <p>The <a href="#command-facet-label" title="command-facet-Label">Label</a> of the command
+  depends on the element. If the element is a <a href="#labeled-control">labeled
+  control</a>, the <code><a href="#textcontent">textContent</a></code> of the first
+  <code><a href="#the-label-element">label</a></code> element in <a href="#tree-order">tree order</a> whose
+  <a href="#labeled-control">labeled control</a> is the element in question is the <a href="#command-facet-label" title="command-facet-Label">Label</a> (in DOM terms, this is the
+  string given by <code><var title="">element</var>.labels[0].textContent</code>). Otherwise, the
+  <a href="#command-facet-label" title="command-facet-Label">Label</a> is the
+  <code><a href="#textcontent">textContent</a></code> of the element itself.</p>
+
+  <p>The <a href="#command-facet-hint" title="command-facet-Hint">Hint</a> of the command
+  is the value of the <code title="attr-title"><a href="#the-title-attribute">title</a></code> attribute
+  of the element. If the attribute is not present, the <a href="#command-facet-hint" title="command-facet-Hint">Hint</a> is the empty string.</p>
+
+  <p>There is no <a href="#command-facet-icon" title="command-facet-Icon">Icon</a> for the
+  command.</p>
+
+  <p>The <a href="#command-facet-accesskey" title="command-facet-AccessKey">AccessKey</a> of the
+  command is the element's <a href="#assigned-access-key">assigned access key</a>.</p>
+
+  <p>The <a href="#command-facet-hiddenstate" title="command-facet-HiddenState">Hidden State</a>
+  of the command is true (hidden) if the element has a <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute, and false
+  otherwise.</p>
+
+  <p>The <a href="#command-facet-disabledstate" title="command-facet-DisabledState">Disabled
+  State</a> facet of the command is always false. (The command is
+  always enabled.)</p>
+
+  <p>The <a href="#command-facet-checkedstate" title="command-facet-CheckedState">Checked State</a>
+  of the command is always false. (The command is never checked.)</p>
+
+  <p>The <a href="#command-facet-action" title="command-facet-Action">Action</a> of the
+  command is to run the <a href="#focusing-steps">focusing steps</a> for the
+  element.</p>
+
   </div><h3 id="miscellaneous-elements"><span class="secno">4.12 </span>Miscellaneous elements</h3><h4 id="the-legend-element"><span class="secno">4.12.1 </span>The <dfn><code>legend</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
    <dd>None.</dd>
    <dt>Contexts in which this element may be used:</dt>
@@ -42951,11 +43048,17 @@
   with a scrollbar would be equivalent, and no less correct.<p>Elements in a section hidden by the <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute are still active,
   e.g. scripts and form controls in such sections still render execute
   and submit respectively. Only their presentation to the user
-  changes.</p><!-- XXX might be worth disabling user interaction event submission
+  changes.<div class="impl">
+
+  <!-- XXX might be worth disabling user interaction event submission
   in hidden areas? e.g. make onmousemove and onclick and form controls
-  not respond to input? --><p>The <dfn id="dom-hidden" title="dom-hidden"><code>hidden</code></dfn> DOM
+  not respond to input? -->
+
+  <p>The <dfn id="dom-hidden" title="dom-hidden"><code>hidden</code></dfn> DOM
   attribute must <a href="#reflect">reflect</a> the content attribute of the
-  same name.<h3 id="activation"><span class="secno">6.3 </span>Activation</h3><!-- v2 idea: HTMLImageElement.click(x, y); or clickPoint(), if
+  same name.</p>
+
+  </div><h3 id="activation"><span class="secno">6.3 </span>Activation</h3><!-- v2 idea: HTMLImageElement.click(x, y); or clickPoint(), if
        click() can't be done in IE; can this be emulated in IE by
        posting a synthetic mouse click event with those X and Y
        coords? (ack Csaba Gabor)
@@ -43361,7 +43464,133 @@
   which the method was called instead. User agents may selectively or
   uniformly ignore calls to this method for usability reasons.</p>
 
-  </div><h3 id="selection"><span class="secno">6.6 </span>The text selection APIs</h3><p>Every <a href="#browsing-context">browsing context</a> has <dfn id="the-selection" title="the
+  </div><h3 id="the-accesskey-attribute"><span class="secno">6.6 </span>The <dfn title="attr-accesskey"><code>accesskey</code></dfn> attribute</h3><p>All elements may have the <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> content attribute set. The
+  <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> attribute's value is
+  used by the user agent as a guide for creating a keyboard shortcut
+  that activates or focuses the element.<p>If specified, the value must be an <a href="#ordered-set-of-unique-space-separated-tokens">ordered set of unique
+  space-separated tokens</a>, each of which must be exactly one
+  Unicode code point in length.<div class="impl">
+
+  <p>An element's <dfn id="assigned-access-key">assigned access key</dfn> is a key combination
+  derived from the element's <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> content attribute as
+  follows:</p>
+
+  <ol><li><p>If the element has no <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> attribute, then the element
+   has no <a href="#assigned-access-key">assigned access key</a>.</li>
+
+   <li><p>Otherwise, the user agent must must <a href="#split-a-string-on-spaces" title="split a
+   string on spaces">split the attribute's value on spaces</a>, and
+   let <var title="">keys</var> be the resulting tokens.</li>
+
+   <li>
+
+    <p>For each value in <var title="">keys</var> in turn, in the
+    order the tokens appeared in the attribute's value, run the
+    following substeps:</p>
+
+    <ol><li><p>If the value is not a string exactly one Unicode code
+     point in length, then skip the remainder of these steps for this
+     value.</li>
+
+     <li><p>If the value does not correspond to a key on the system's
+     keyboard, then skip the remainder of these steps for this
+     value.</li>
+
+     <li><p>If the user agent can find a combination of modifier keys
+     that, with the key that corresponds to the value given in the
+     attribute, can be used as a shortcut key, then the user agent may
+     assign that combination of keys as the element's <a href="#assigned-access-key">assigned
+     access key</a> and abort these steps.</li>
+
+    </ol></li>
+
+   <li><p>If none of the values (if any) result in an access key being
+   assigned, then the element has no <a href="#assigned-access-key">assigned access
+   key</a>.</li>
+
+  </ol><p>Once a user agent has selected and assigned an access key for an
+  element, the user agent should not change the element's
+  <a href="#assigned-access-key">assigned access key</a> unless the <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> content attribute is changed
+  or the element is moved to another <code>Document</code>.</p>
+
+  <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>, 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
+  well, e.g. in a menu displayed in response to a specific key
+  combination.</p>
+
+  </div><div class="impl">
+
+  <p>The <dfn id="dom-accesskey" title="dom-accessKey"><code>accessKey</code></dfn> DOM
+  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> DOM
+  attribute must return a string that represents the element's
+  <a href="#assigned-access-key">assigned access key</a>, if any. If the element does not
+  have one, then the DOM attribute must return the empty string.</p>
+
+  </div><div class="example">
+
+   <p>In the following example, a variety of links are given with
+   access keys so that keyboard users familiar with the site can
+   more quickly navigate to the relevant pages:</p>
+
+   <pre>&lt;nav&gt;
+ &lt;p&gt;
+  &lt;a title="Consortium Activities" accesskey="A" href="/Consortium/activities"&gt;Activities&lt;/a&gt; |
+  &lt;a title="Technical Reports and Recommendations" accesskey="T" href="/TR/"&gt;Technical Reports&lt;/a&gt; |
+  &lt;a title="Alphabetical Site Index" accesskey="S" href="/Consortium/siteindex"&gt;Site Index&lt;/a&gt; |
+  &lt;a title="About This Site" accesskey="B" href="/Consortium/"&gt;About Consortium&lt;/a&gt; |
+  &lt;a title="Contact Consortium" accesskey="C" href="/Consortium/contact"&gt;Contact&lt;/a&gt;
+ &lt;/p&gt;
+&lt;/nav&gt;</pre>
+
+  </div><div class="example">
+
+   <p>In the following example, the search field is given two possible
+   access keys, "s" and "0" (in that order). A user agent on a device
+   with a full keyboard might pick
+   <kbd><kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd></kbd> as the
+   shortcut key, while a user agent on a small device with just a
+   numeric keypad might pick just the plain unadorned key
+   <kbd><kbd>0</kbd></kbd>:</p>
+
+   <pre>&lt;form action="/search"&gt;
+ &lt;label&gt;Search: &lt;input type="search" name="q" accesskey="s 0"&gt;&lt;/label&gt;
+ &lt;input type="submit"&gt;
+&lt;/form&gt;</pre>
+
+  </div><div class="example">
+
+   <p>In the following example, a button has possible access keys
+   described. A script then tries to update the button's label to
+   advertise the key combination the user agent selected.</p>
+
+   <pre>&lt;input type=submit accesskey="N @ 1" value="Compose"&gt;
+...
+&lt;script&gt;
+ function labelButton(button) {
+   if (button.accessKeyLabel)
+     button.value += ' (' + button.accessKeyLabel + ')';
+ }
+ var inputs = document.getElementsByTagName('input');
+ for (var i = 0; i &lt; inputs.length; i += 1) {
+   if (inputs[i].type == "submit")
+     labelButton(inputs[i]);
+ }
+&lt;/script&gt;</pre>
+
+   <p>On one user agent, the button's label might become
+   "<samp>Compose (&#8984;N)</samp>". On another, it might become
+   "<samp>Compose (Alt+&#8679;+1)</samp>". If the user agent doesn't
+   assign a key, it will be just "<samp>Compose</samp>". The exact
+   string depends on what the <a href="#assigned-access-key">assigned access key</a> is, and
+   on how the user agent represents that key combination.</p>
+
+  </div><h3 id="selection"><span class="secno">6.7 </span>The text selection APIs</h3><p>Every <a href="#browsing-context">browsing context</a> has <dfn id="the-selection" title="the
   selection">a selection</dfn>. The selection can be empty, and the
   selection can have more than one range (a disjointed selection). The
   user agent should allow the user to change the selection. User
@@ -43415,7 +43644,7 @@
   are presented to the user. The Selectors specification, in
   conjunction with CSS, can be used to style text selections using the
   <code title="selector-selection">::selection</code>
-  pseudo-element. <a href="#references">[SELECTORS]</a> <a href="#references">[CSS21]</a><h4 id="documentSelection"><span class="secno">6.6.1 </span>APIs for the browsing context selection</h4><dl class="domintro"><dt><var title="">window</var> . <code title="dom-getSelection"><a href="#dom-getselection">getSelection</a></code>()</dt>
+  pseudo-element. <a href="#references">[SELECTORS]</a> <a href="#references">[CSS21]</a><h4 id="documentSelection"><span class="secno">6.7.1 </span>APIs for the browsing context selection</h4><dl class="domintro"><dt><var title="">window</var> . <code title="dom-getSelection"><a href="#dom-getselection">getSelection</a></code>()</dt>
    <dt><var title="">document</var> . <code title="dom-document-getSelection"><a href="#dom-document-getselection">getSelection</a></code>()</dt>
 
    <dd>
@@ -43717,7 +43946,7 @@
   </div><!-- v2DGS:
   <p class="note">The <code>Selection</code> interface has no relation
   to the <code>DataGridSelection</code> interface.</p>
-  --><h4 id="textFieldSelection"><span class="secno">6.6.2 </span>APIs for the text field selections</h4><!-- v2 idea: DOM Range APIs to expose the textarea/input edited
+  --><h4 id="textFieldSelection"><span class="secno">6.7.2 </span>APIs for the text field selections</h4><!-- v2 idea: DOM Range APIs to expose the textarea/input edited
   value (ack martijnw) --><p>The <code><a href="#the-input-element">input</a></code> and <code><a href="#the-textarea-element">textarea</a></code> elements define
   the following members in their DOM interfaces for handling their
   text selection:<pre class="idl">  void <a href="#dom-textarea-input-select" title="dom-textarea/input-select">select</a>();
@@ -43822,7 +44051,7 @@
   </div><p>Characters with no visible rendering, such as U+200D ZERO WIDTH
   JOINER, still count as characters. Thus, for instance, the selection
   can include just an invisible character, and the text insertion
-  cursor can be placed to one side or another of such a character.<h3 id="contenteditable"><span class="secno">6.7 </span>The <code title="attr-contenteditable"><a href="#attr-contenteditable">contenteditable</a></code> attribute</h3><p>The <dfn id="attr-contenteditable" title="attr-contenteditable"><code>contenteditable</code></dfn>
+  cursor can be placed to one side or another of such a character.<h3 id="contenteditable"><span class="secno">6.8 </span>The <code title="attr-contenteditable"><a href="#attr-contenteditable">contenteditable</a></code> attribute</h3><p>The <dfn id="attr-contenteditable" title="attr-contenteditable"><code>contenteditable</code></dfn>
   attribute is an <a href="#enumerated-attribute">enumerated attribute</a> whose keywords are
   the empty string, <code title="">true</code>, and <code title="">false</code>. The empty string and the <code title="">true</code> keyword map to the <i>true</i> state. The <code title="">false</code> keyword maps to the <i>false</i> state. In
   addition, there is a third state, the <i>inherit</i> state, which is
@@ -43920,7 +44149,7 @@
 
   </div><div class="impl">
 
-  <h4 id="user-editing-actions"><span class="secno">6.7.1 </span>User editing actions</h4>
+  <h4 id="user-editing-actions"><span class="secno">6.8.1 </span>User editing actions</h4>
 
   <p>There are several actions that the user agent should allow the
   user to perform while the user is interacting with an editing
@@ -44102,7 +44331,7 @@
   or programmatically (e.g. by <code title="dom-document-execCommand"><a href="#execCommand">execCommand()</a></code> commands),
   must fire mutation events as appropriate.</p>
 
-  </div><h4 id="making-entire-documents-editable"><span class="secno">6.7.2 </span>Making entire documents editable</h4><div class="impl">
+  </div><h4 id="making-entire-documents-editable"><span class="secno">6.8.2 </span>Making entire documents editable</h4><div class="impl">
 
   <p>Documents have a <dfn id="designMode" title="dom-document-designMode"><code>designMode</code></dfn>, which
   can be either enabled or disabled.</p>
@@ -44136,7 +44365,7 @@
   <p>The last state set must persist until the document is destroyed
   or the state is changed. Initially, documents must have their <code title="dom-document-designMode"><a href="#designMode">designMode</a></code> disabled.</p>
 
-  </div><h3 id="spelling-and-grammar-checking"><span class="secno">6.8 </span>Spelling and grammar checking</h3><div class="impl">
+  </div><h3 id="spelling-and-grammar-checking"><span class="secno">6.9 </span>Spelling and grammar checking</h3><div class="impl">
 
   <p>User agents can support the checking of spelling and grammar of
   editable text, either in form controls (such as the value of
@@ -44308,7 +44537,7 @@
 
   </div>
 
-  </div><h3 id="dnd"><span class="secno">6.9 </span><dfn>Drag and drop</dfn></h3><!--XXX
+  </div><h3 id="dnd"><span class="secno">6.10 </span><dfn>Drag and drop</dfn></h3><!--XXX
 
 http://msdn.microsoft.com/workshop/author/datatransfer/overview.asp
 http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/clipboarddata.asp
@@ -44355,7 +44584,7 @@
   not canceled, there must be at least one element in the middle
   step).</p>
 
-  </div><h4 id="introduction-4"><span class="secno">6.9.1 </span>Introduction</h4><p><em>This section is non-normative.</em><p class="XXX">It's also currently non-existent.<h4 id="the-dragevent-and-datatransfer-interfaces"><span class="secno">6.9.2 </span>The <code><a href="#dragevent">DragEvent</a></code> and <code><a href="#datatransfer">DataTransfer</a></code> interfaces</h4><p>The drag-and-drop processing model involves several events. They
+  </div><h4 id="introduction-4"><span class="secno">6.10.1 </span>Introduction</h4><p><em>This section is non-normative.</em><p class="XXX">It's also currently non-existent.<h4 id="the-dragevent-and-datatransfer-interfaces"><span class="secno">6.10.2 </span>The <code><a href="#dragevent">DragEvent</a></code> and <code><a href="#datatransfer">DataTransfer</a></code> interfaces</h4><p>The drag-and-drop processing model involves several events. They
   all use the <code><a href="#dragevent">DragEvent</a></code> interface.<pre class="idl">interface <dfn id="dragevent">DragEvent</dfn> : MouseEvent {
   readonly attribute <a href="#datatransfer">DataTransfer</a> <a href="#dom-dragevent-datatransfer" title="dom-DragEvent-dataTransfer">dataTransfer</a>;
 
@@ -44558,7 +44787,7 @@
   current rendering of the elements added, whereas the former uses the
   exact specified image.</p>
 
-  </div><h4 id="events-fired-during-a-drag-and-drop-action"><span class="secno">6.9.3 </span>Events fired during a drag-and-drop action</h4><p>The following events are involved in the drag-and-drop
+  </div><h4 id="events-fired-during-a-drag-and-drop-action"><span class="secno">6.10.3 </span>Events fired during a drag-and-drop action</h4><p>The following events are involved in the drag-and-drop
   model. <span class="impl">Whenever the processing model described
   below causes one of these events to be fired, the event fired must
   use the <code><a href="#dragevent">DragEvent</a></code> interface defined above, must have
@@ -44675,7 +44904,7 @@
     <td><code title="">copy</code></td>
    </table></div><div class="impl">
 
-  <h4 id="drag-and-drop-processing-model"><span class="secno">6.9.4 </span>Drag-and-drop processing model</h4>
+  <h4 id="drag-and-drop-processing-model"><span class="secno">6.10.4 </span>Drag-and-drop processing model</h4>
 
   <p>When the user attempts to begin a drag operation, the user agent
   must first determine what is being dragged. If the drag operation
@@ -45055,7 +45284,7 @@
 
   </ol></div><div class="impl">
 
-  <h5 id="when-the-drag-and-drop-operation-starts-or-ends-in-another-document"><span class="secno">6.9.4.1 </span>When the drag-and-drop operation starts or ends in another
+  <h5 id="when-the-drag-and-drop-operation-starts-or-ends-in-another-document"><span class="secno">6.10.4.1 </span>When the drag-and-drop operation starts or ends in another
   document</h5>
 
   <p>The model described above is independent of which
@@ -45070,7 +45299,7 @@
 
   </div><div class="impl">
 
-  <h5 id="when-the-drag-and-drop-operation-starts-or-ends-in-another-application"><span class="secno">6.9.4.2 </span>When the drag-and-drop operation starts or ends in another
+  <h5 id="when-the-drag-and-drop-operation-starts-or-ends-in-another-application"><span class="secno">6.10.4.2 </span>When the drag-and-drop operation starts or ends in another
   application</h5>
 
   <p>If the drag is initiated in another application, the <a href="#source-node">source
@@ -45093,7 +45322,7 @@
   drag-and-drop operation being started or ended in another document
   from another domain.</p>
 
-  </div><h4 id="the-draggable-attribute"><span class="secno">6.9.5 </span>The <dfn title="attr-draggable"><code>draggable</code></dfn> attribute</h4><p>All elements may have the <code title="attr-draggable"><a href="#the-draggable-attribute">draggable</a></code> content attribute set. The
+  </div><h4 id="the-draggable-attribute"><span class="secno">6.10.5 </span>The <dfn title="attr-draggable"><code>draggable</code></dfn> attribute</h4><p>All elements may have the <code title="attr-draggable"><a href="#the-draggable-attribute">draggable</a></code> content attribute set. The
   <code title="attr-draggable"><a href="#the-draggable-attribute">draggable</a></code> attribute is an
   <a href="#enumerated-attribute">enumerated attribute</a>. It has three states. The first
   state is <i>true</i> and it has the keyword <code title="">true</code>. The second state is <i>false</i> and it has
@@ -45143,14 +45372,14 @@
   value true, the <code title="attr-draggable"><a href="#the-draggable-attribute">draggable</a></code>
   content attribute must be set to the literal value <code title="">true</code>.</p>
 
-  </div><h4 id="copy-and-paste"><span class="secno">6.9.6 </span>Copy and paste</h4><p>Copy-and-paste is a form of drag-and-drop: the "copy" part is
+  </div><h4 id="copy-and-paste"><span class="secno">6.10.6 </span>Copy and paste</h4><p>Copy-and-paste is a form of drag-and-drop: the "copy" part is
   equivalent to dragging content to another application (the
   "clipboard"), and the "paste" part is equivalent to dragging content
   <em>from</em> another application.<p>Select-and-paste (a model used by mouse operations in the X
   Window System) is equivalent to a drag-and-drop operation where the
   source is the selection.<div class="impl">
 
-  <h5 id="copy-to-clipboard"><span class="secno">6.9.6.1 </span>Copy to clipboard</h5>
+  <h5 id="copy-to-clipboard"><span class="secno">6.10.6.1 </span>Copy to clipboard</h5>
 
   <p>When the user invokes a copy operation, the user agent must act
   as if the user had invoked a drag on the current selection. If the
@@ -45164,14 +45393,14 @@
   operations (e.g. updating the clipboard).</p>
 
 
-  <h5 id="cut-to-clipboard"><span class="secno">6.9.6.2 </span>Cut to clipboard</h5>
+  <h5 id="cut-to-clipboard"><span class="secno">6.10.6.2 </span>Cut to clipboard</h5>
 
   <p>When the user invokes a cut operation, the user agent must act as
   if the user had invoked a copy operation (see the previous section),
   followed, if the copy was completed successfully, by <a href="#contenteditable-delete">a selection delete operation</a>.</p>
 
 
-  <h5 id="paste-from-clipboard"><span class="secno">6.9.6.3 </span>Paste from clipboard</h5>
+  <h5 id="paste-from-clipboard"><span class="secno">6.10.6.3 </span>Paste from clipboard</h5>
 
   <p>When the user invokes a clipboard paste operation, the user agent
   must act as if the user had invoked a drag on a hypothetical
@@ -45185,7 +45414,7 @@
   canceling it.</p>
 
 
-  <h5 id="paste-from-selection"><span class="secno">6.9.6.4 </span>Paste from selection</h5>
+  <h5 id="paste-from-selection"><span class="secno">6.10.6.4 </span>Paste from selection</h5>
 
   <p>When the user invokes a selection paste operation, the user agent
   must act as if the user had invoked a drag on the current selection,
@@ -45195,7 +45424,7 @@
 
   </div><div class="impl">
 
-  <h4 id="security-risks-in-the-drag-and-drop-model"><span class="secno">6.9.7 </span>Security risks in the drag-and-drop model</h4>
+  <h4 id="security-risks-in-the-drag-and-drop-model"><span class="secno">6.10.7 </span>Security risks in the drag-and-drop model</h4>
 
   <p>User agents must not make the data added to the
   <code><a href="#datatransfer">DataTransfer</a></code> object during the <code title="event-dragstart"><a href="#event-dragstart">dragstart</a></code> event available to scripts
@@ -45218,9 +45447,9 @@
   data to be dragged from sensitive sources and dropped into hostile
   documents without the user's consent.</p>
 
-  </div><h3 id="undo"><span class="secno">6.10 </span><dfn>Undo history</dfn></h3><p class="XXX">There has got to be a better way of doing this, surely.<h4 id="introduction-5"><span class="secno">6.10.1 </span>Introduction</h4><p class="XXX">...<div class="impl">
+  </div><h3 id="undo"><span class="secno">6.11 </span><dfn>Undo history</dfn></h3><p class="XXX">There has got to be a better way of doing this, surely.<h4 id="introduction-5"><span class="secno">6.11.1 </span>Introduction</h4><p class="XXX">...<div class="impl">
 
-  <h4 id="definitions-2"><span class="secno">6.10.2 </span>Definitions</h4>
+  <h4 id="definitions-2"><span class="secno">6.11.2 </span>Definitions</h4>
 
   <p>The user agent must associate an <dfn id="undo-transaction-history">undo transaction
   history</dfn> with each <code><a href="#htmldocument">HTMLDocument</a></code> object.</p>
@@ -45258,7 +45487,7 @@
   interactions with server-side state, or in the implementation of a
   drawing tool).</p>
 
-  </div><h4 id="the-undomanager-interface"><span class="secno">6.10.3 </span>The <code><a href="#undomanager">UndoManager</a></code> interface</h4><div class="impl">
+  </div><h4 id="the-undomanager-interface"><span class="secno">6.11.3 </span>The <code><a href="#undomanager">UndoManager</a></code> interface</h4><div class="impl">
 
   <div class="XXX">
 
@@ -45453,7 +45682,7 @@
 
   </div><div class="impl">
 
-  <h4 id="undo:-moving-back-in-the-undo-transaction-history"><span class="secno">6.10.4 </span><dfn title="do-undo">Undo: moving back in the undo transaction history</dfn></h4>
+  <h4 id="undo:-moving-back-in-the-undo-transaction-history"><span class="secno">6.11.4 </span><dfn title="do-undo">Undo: moving back in the undo transaction history</dfn></h4>
 
   <p>When the user invokes an undo operation, or when the <code title="dom-document-execCommand"><a href="#execCommand">execCommand()</a></code> method is
   called with the <code title="command-undo"><a href="#command-undo">undo</a></code> command, the
@@ -45490,7 +45719,7 @@
   command to undo his undo.</p>
 
 
-  <h4 id="redo:-moving-forward-in-the-undo-transaction-history"><span class="secno">6.10.5 </span><dfn title="do-redo">Redo: moving forward in the undo transaction history</dfn></h4>
+  <h4 id="redo:-moving-forward-in-the-undo-transaction-history"><span class="secno">6.11.5 </span><dfn title="do-redo">Redo: moving forward in the undo transaction history</dfn></h4>
 
   <p>When the user invokes a redo operation, or when the <code title="dom-document-execCommand"><a href="#execCommand">execCommand()</a></code> method is
   called with the <code title="command-redo"><a href="#command-redo">redo</a></code> command, the
@@ -45524,7 +45753,7 @@
   object, using the <a href="#undo-object">undo object</a> entry's associated undo
   object as the event's data.</p>
 
-  </div><h4 id="the-undomanagerevent-interface-and-the-undo-and-redo-events"><span class="secno">6.10.6 </span>The <code><a href="#undomanagerevent">UndoManagerEvent</a></code> interface and the <code title="event-undo"><a href="#event-undo">undo</a></code> and <code title="event-redo"><a href="#event-redo">redo</a></code> events</h4><pre class="idl">interface <dfn id="undomanagerevent">UndoManagerEvent</dfn> : Event {
+  </div><h4 id="the-undomanagerevent-interface-and-the-undo-and-redo-events"><span class="secno">6.11.6 </span>The <code><a href="#undomanagerevent">UndoManagerEvent</a></code> interface and the <code title="event-undo"><a href="#event-undo">undo</a></code> and <code title="event-redo"><a href="#event-redo">redo</a></code> events</h4><pre class="idl">interface <dfn id="undomanagerevent">UndoManagerEvent</dfn> : Event {
   readonly attribute any <a href="#dom-undomanagerevent-data" title="dom-UndoManagerEvent-data">data</a>;
   void <a href="#dom-undomanagerevent-initundomanagerevent" title="dom-UndoManagerEvent-initUndoManagerEvent">initUndoManagerEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dataArg);
   void <span title="dom-UndoManagerEvent-initUndoManagerEventNS">initUndoManagerEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dataArg);
@@ -45554,7 +45783,7 @@
 
   </div><div class="impl">
 
-  <h4 id="implementation-notes"><span class="secno">6.10.7 </span>Implementation notes</h4>
+  <h4 id="implementation-notes"><span class="secno">6.11.7 </span>Implementation notes</h4>
 
   <p>How user agents present the above conceptual model to the user is
   not defined. The undo interface could be a filtered view of the
@@ -45571,7 +45800,7 @@
   described in this section, however, such that to a script there is
   no detectable difference.</p>
 
-  </div><h3 id="editing-apis"><span class="secno">6.11 </span>Editing APIs</h3><dl class="domintro"><dt><var title="">document</var> . <code title="dom-document-execCommand"><a href="#execCommand">execCommand</a></code>(<var title="">commandId</var> [, <var title="">showUI</var> [, <var title="">value</var> ] ] )</dt>
+  </div><h3 id="editing-apis"><span class="secno">6.12 </span>Editing APIs</h3><dl class="domintro"><dt><var title="">document</var> . <code title="dom-document-execCommand"><a href="#execCommand">execCommand</a></code>(<var title="">commandId</var> [, <var title="">showUI</var> [, <var title="">value</var> ] ] )</dt>
 
    <dd>
 
Received on Sunday, 3 May 2009 01:55:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 3 May 2009 01:55:31 GMT