W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2010

html5/spec Overview.html,1.4495,1.4496

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 13 Oct 2010 20:19:09 +0000
To: public-html-commits@w3.org
Message-Id: <E1P67n3-0004Y7-QS@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv17469

Modified Files:
	Overview.html 
Log Message:
Move scrollIntoView() to CSSOM View and update the other scroll algorithm to use the CSSOM View definition. (whatwg r5620)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4495
retrieving revision 1.4496
diff -u -d -r1.4495 -r1.4496
--- Overview.html	13 Oct 2010 18:45:08 -0000	1.4495
+++ Overview.html	13 Oct 2010 20:19:05 -0000	1.4496
@@ -1053,45 +1053,44 @@
   <ol>
    <li><a href="#the-hidden-attribute"><span class="secno">7.1 </span>The <code>hidden</code> attribute</a></li>
    <li><a href="#activation"><span class="secno">7.2 </span>Activation</a></li>
-   <li><a href="#scrolling-elements-into-view"><span class="secno">7.3 </span>Scrolling elements into view</a></li>
-   <li><a href="#focus"><span class="secno">7.4 </span>Focus</a>
+   <li><a href="#focus"><span class="secno">7.3 </span>Focus</a>
     <ol>
-     <li><a href="#sequential-focus-navigation-and-the-tabindex-attribute"><span class="secno">7.4.1 </span>Sequential focus navigation and the <code title="attr-tabindex">tabindex</code> attribute</a></li>
-     <li><a href="#focus-management"><span class="secno">7.4.2 </span>Focus management</a></li>
-     <li><a href="#document-level-focus-apis"><span class="secno">7.4.3 </span>Document-level focus APIs</a></li>
-     <li><a href="#element-level-focus-apis"><span class="secno">7.4.4 </span>Element-level focus APIs</a></ol></li>
-   <li><a href="#assigning-keyboard-shortcuts"><span class="secno">7.5 </span>Assigning keyboard shortcuts</a>
+     <li><a href="#sequential-focus-navigation-and-the-tabindex-attribute"><span class="secno">7.3.1 </span>Sequential focus navigation and the <code title="attr-tabindex">tabindex</code> attribute</a></li>
+     <li><a href="#focus-management"><span class="secno">7.3.2 </span>Focus management</a></li>
+     <li><a href="#document-level-focus-apis"><span class="secno">7.3.3 </span>Document-level focus APIs</a></li>
+     <li><a href="#element-level-focus-apis"><span class="secno">7.3.4 </span>Element-level focus APIs</a></ol></li>
+   <li><a href="#assigning-keyboard-shortcuts"><span class="secno">7.4 </span>Assigning keyboard shortcuts</a>
     <ol>
-     <li><a href="#introduction-5"><span class="secno">7.5.1 </span>Introduction</a></li>
-     <li><a href="#the-accesskey-attribute"><span class="secno">7.5.2 </span>The <code>accesskey</code> attribute</a></li>
-     <li><a href="#processing-model-3"><span class="secno">7.5.3 </span>Processing model</a></ol></li>
-   <li><a href="#contenteditable"><span class="secno">7.6 </span>The <code title="attr-contenteditable">contenteditable</code> attribute</a>
+     <li><a href="#introduction-5"><span class="secno">7.4.1 </span>Introduction</a></li>
+     <li><a href="#the-accesskey-attribute"><span class="secno">7.4.2 </span>The <code>accesskey</code> attribute</a></li>
+     <li><a href="#processing-model-3"><span class="secno">7.4.3 </span>Processing model</a></ol></li>
+   <li><a href="#contenteditable"><span class="secno">7.5 </span>The <code title="attr-contenteditable">contenteditable</code> attribute</a>
     <ol>
-     <li><a href="#user-editing-actions"><span class="secno">7.6.1 </span>User editing actions</a></li>
-     <li><a href="#making-entire-documents-editable"><span class="secno">7.6.2 </span>Making entire documents editable</a></ol></li>
-   <li><a href="#spelling-and-grammar-checking"><span class="secno">7.7 </span>Spelling and grammar checking</a></li>
-   <li><a href="#dnd"><span class="secno">7.8 </span>Drag and drop</a>
+     <li><a href="#user-editing-actions"><span class="secno">7.5.1 </span>User editing actions</a></li>
+     <li><a href="#making-entire-documents-editable"><span class="secno">7.5.2 </span>Making entire documents editable</a></ol></li>
+   <li><a href="#spelling-and-grammar-checking"><span class="secno">7.6 </span>Spelling and grammar checking</a></li>
+   <li><a href="#dnd"><span class="secno">7.7 </span>Drag and drop</a>
     <ol>
-     <li><a href="#introduction-6"><span class="secno">7.8.1 </span>Introduction</a></li>
-     <li><a href="#the-dragevent-and-datatransfer-interfaces"><span class="secno">7.8.2 </span>The <code>DragEvent</code> and <code>DataTransfer</code> interfaces</a></li>
-     <li><a href="#dndevents"><span class="secno">7.8.3 </span>Events fired during a drag-and-drop action</a></li>
-     <li><a href="#drag-and-drop-processing-model"><span class="secno">7.8.4 </span>Drag-and-drop processing model</a>
+     <li><a href="#introduction-6"><span class="secno">7.7.1 </span>Introduction</a></li>
+     <li><a href="#the-dragevent-and-datatransfer-interfaces"><span class="secno">7.7.2 </span>The <code>DragEvent</code> and <code>DataTransfer</code> interfaces</a></li>
+     <li><a href="#dndevents"><span class="secno">7.7.3 </span>Events fired during a drag-and-drop action</a></li>
+     <li><a href="#drag-and-drop-processing-model"><span class="secno">7.7.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">7.8.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">7.7.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">7.8.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">7.7.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">7.8.5 </span>The <code>draggable</code> attribute</a></li>
-     <li><a href="#security-risks-in-the-drag-and-drop-model"><span class="secno">7.8.6 </span>Security risks in the drag-and-drop model</a></ol></li>
-   <li><a href="#undo"><span class="secno">7.9 </span>Undo history</a>
+     <li><a href="#the-draggable-attribute"><span class="secno">7.7.5 </span>The <code>draggable</code> attribute</a></li>
+     <li><a href="#security-risks-in-the-drag-and-drop-model"><span class="secno">7.7.6 </span>Security risks in the drag-and-drop model</a></ol></li>
+   <li><a href="#undo"><span class="secno">7.8 </span>Undo history</a>
     <ol>
-     <li><a href="#definitions-2"><span class="secno">7.9.1 </span>Definitions</a></li>
-     <li><a href="#the-undomanager-interface"><span class="secno">7.9.2 </span>The <code>UndoManager</code> interface</a></li>
-     <li><a href="#undo:-moving-back-in-the-undo-transaction-history"><span class="secno">7.9.3 </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">7.9.4 </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">7.9.5 </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">7.9.6 </span>Implementation notes</a></ol></li>
-   <li><a href="#editing-apis"><span class="secno">7.10 </span>Editing APIs</a></ol></li>
+     <li><a href="#definitions-2"><span class="secno">7.8.1 </span>Definitions</a></li>
+     <li><a href="#the-undomanager-interface"><span class="secno">7.8.2 </span>The <code>UndoManager</code> interface</a></li>
+     <li><a href="#undo:-moving-back-in-the-undo-transaction-history"><span class="secno">7.8.3 </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">7.8.4 </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">7.8.5 </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">7.8.6 </span>Implementation notes</a></ol></li>
+   <li><a href="#editing-apis"><span class="secno">7.9 </span>Editing APIs</a></ol></li>
  <li><a href="#syntax"><span class="secno">8 </span>The HTML syntax</a>
   <ol>
    <li><a href="#writing"><span class="secno">8.1 </span>Writing HTML documents</a>
@@ -8032,8 +8031,6 @@
   // <a href="#editing">user interaction</a>
            attribute boolean <a href="#dom-hidden" title="dom-hidden">hidden</a>;
   void <a href="#dom-click" title="dom-click">click</a>();
-  void <a href="#dom-scrollintoview" title="dom-scrollIntoView">scrollIntoView</a>();
-  void <a href="#dom-scrollintoview" title="dom-scrollIntoView">scrollIntoView</a>(in boolean top);
            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>();
@@ -44749,10 +44746,11 @@
 
   <hr><p>When the user agent is required to <dfn id="scroll-to-the-fragment-identifier">scroll to the fragment
   identifier</dfn>, it must change the scrolling position of the
-  document, or perform some other action, such that <a href="#the-indicated-part-of-the-document">the
-  indicated part of the document</a> is brought to the user's
-  attention. If there is no indicated part, then the user agent must
-  not scroll anywhere.</p>
+  document using the <span>scroll an element into view</span>
+  algorithm defined in the CSSOM View specification, or perform some
+  other action, such that <a href="#the-indicated-part-of-the-document">the indicated part of the
+  document</a> is brought to the user's attention. If there is no
+  indicated part, then the user agent must not scroll anywhere. <a href="#refsCSSOMVIEW">[CSSOMVIEW]</a></p>
 
   <p><dfn id="the-indicated-part-of-the-document">The indicated part of the document</dfn> is the one that the
   fragment identifier, if any, identifies. The semantics of the
@@ -49573,48 +49571,7 @@
    <li><p>Set the <var title="">click in progress</var> flag on the
    element to false.</li>
 
-  </ol></div><h3 id="scrolling-elements-into-view"><span class="secno">7.3 </span>Scrolling elements into view</h3><!-- maybe this should move to [CSSOM] --><dl class="domintro"><dt><var title="">element</var> . <code title="dom-scrollIntoView"><a href="#dom-scrollintoview">scrollIntoView</a></code>( [ <var title="">top</var> ] )</dt>
-
-   <dd>
-
-    <p>Scrolls the element into view. If the <var title="">top</var>
-    argument is true, then the element will be scrolled to the top of
-    the viewport, otherwise it'll be scrolled to the bottom. The
-    default is the top.</p>
-
-   </dd>
-
-  </dl><div class="impl">
-
-  <p>The <dfn id="dom-scrollintoview" title="dom-scrollIntoView"><code>scrollIntoView([<var title="">top</var>])</code></dfn> method, when called, must cause
-  the element on which the method was called to have the attention of
-  the user called to it.</p>
-
-  <p class="note">In a speech browser, this could happen by having the
-  current playback position move to the start of the given
-  element.</p>
-
-  <p>If the element in question cannot be brought to the user's
-  attention, e.g. because it is <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code>, or is not <a href="#being-rendered">being
-  rendered</a>, then the user agent must do nothing instead.</p>
-
-  <p>In visual user agents, if the argument is present and has the
-  value false, the user agent should scroll the element into view such
-  that both the bottom and the top of the element are in the viewport,
-  with the bottom of the element aligned with the bottom of the
-  viewport. If it isn't possible to show the entire element in that
-  way, or if the argument is omitted or is true, then the user agent
-  should instead align the top of the element with the top of the
-  viewport. If the entire scrollable part of the content is visible
-  all at once (e.g. if a page is shorter than the viewport), then the
-  user agent should not scroll anything. Visual user agents should
-  further scroll horizontally as necessary to bring the element to the
-  attention of the user.</p>
-
-  <p>Non-visual user agents may ignore the argument, or may treat it
-  in some media-specific manner most useful to the user.</p>
-
-  </div><h3 id="focus"><span class="secno">7.4 </span>Focus</h3><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%20%0A...%3Cform%3E%3Cinput%20name%3Da%20onfocus%3D%22value%2B%3D1%3Bd.name%3D%27a%27%3Bname%3D%27d%27%3Bb.focus()%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22value%2B%3D1%3Bc.focus()%22%3E%0A%3Cinput%20name%3Dc%20onfocus%3D%22value%2B%3D1%3Bd.focus()%22%3E%0A%3Cinput%20name%3Dd%20onfocus%3D%22value%2B%3D1%3Ba.focus()%22%3E --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onfocus%3D%22t.value%2B%3D%27af1%20%27%3Bb.focus()%3Balert(document.activeElement.name)%3Bt.value%2B%3D%27af2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27ab%20%27%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D%27bf1%20%27%3Bc.focus()%3Bt.value%2B%3D%27bf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27bb%20%27%3B%22%3E%0A%3Cinput%20name%3Dc%20onfocus%3D%22t.value%2B%3D%27cf1%20%27%3Bc.focus()%3Bt.value%2B%3D%27cf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27cb%20%27%3B%22%3E%0A --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cbody%20onload%3D%22document.forms%5B0%5D.a.focus()%22%3E%0A...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onblur%3D%22t.value%2B%3D'ab%20'%3B%20b.focus()%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D'bf1%20'%3Ba.focus()%3Bt.value%2B%3D'bf2%20'%3B%22%20onblur%3D%22t.value%2B%3D'bb%20'%3B%22%3E --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cbody%3E...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onfocus%3D%22t.value%2B%3D%27af%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27ab1%20%27%3Bb.focus()%3Bt.value%2B%3D%27ab2%20%27%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D%27bf1%20%27%3Ba.focus()%3Bt.value%2B%3D%27bf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27bb%20%27%3B%22%3E --><!-- v2: more things to define, if no other specs define them:
+  </ol></div><h3 id="focus"><span class="secno">7.3 </span>Focus</h3><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%20%0A...%3Cform%3E%3Cinput%20name%3Da%20onfocus%3D%22value%2B%3D1%3Bd.name%3D%27a%27%3Bname%3D%27d%27%3Bb.focus()%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22value%2B%3D1%3Bc.focus()%22%3E%0A%3Cinput%20name%3Dc%20onfocus%3D%22value%2B%3D1%3Bd.focus()%22%3E%0A%3Cinput%20name%3Dd%20onfocus%3D%22value%2B%3D1%3Ba.focus()%22%3E --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onfocus%3D%22t.value%2B%3D%27af1%20%27%3Bb.focus()%3Balert(document.activeElement.name)%3Bt.value%2B%3D%27af2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27ab%20%27%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D%27bf1%20%27%3Bc.focus()%3Bt.value%2B%3D%27bf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27bb%20%27%3B%22%3E%0A%3Cinput%20name%3Dc%20onfocus%3D%22t.value%2B%3D%27cf1%20%27%3Bc.focus()%3Bt.value%2B%3D%27cf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27cb%20%27%3B%22%3E%0A --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cbody%20onload%3D%22document.forms%5B0%5D.a.focus()%22%3E%0A...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onblur%3D%22t.value%2B%3D'ab%20'%3B%20b.focus()%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D'bf1%20'%3Ba.focus()%3Bt.value%2B%3D'bf2%20'%3B%22%20onblur%3D%22t.value%2B%3D'bb%20'%3B%22%3E --><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cbody%3E...%3Cform%3E%0A%3Ctextarea%20name%3Dt%20cols%3D100%20rows%3D3%3E%3C%2Ftextarea%3E%3Cp%3E%0A%3Cinput%20name%3Da%20onfocus%3D%22t.value%2B%3D%27af%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27ab1%20%27%3Bb.focus()%3Bt.value%2B%3D%27ab2%20%27%3B%22%3E%0A%3Cinput%20name%3Db%20onfocus%3D%22t.value%2B%3D%27bf1%20%27%3Ba.focus()%3Bt.value%2B%3D%27bf2%20%27%3B%22%20onblur%3D%22t.value%2B%3D%27bb%20%27%3B%22%3E --><!-- v2: more things to define, if no other specs define them:
    - define onfocus/onblur behaviour for Window
    - Other things to look at are IE's focus APIs (HTMLElement.setActive(),
      onBeforeActivate, onActivate, onBeforeDeactivate, onDeactivate):
@@ -49643,7 +49600,7 @@
   <p class="note">When an element is focused, the element matches the
   CSS <code>:focus</code> pseudo-class.</p>
 
-  </div><h4 id="sequential-focus-navigation-and-the-tabindex-attribute"><span class="secno">7.4.1 </span>Sequential focus navigation and the <code title="attr-tabindex"><a href="#attr-tabindex">tabindex</a></code> attribute</h4><p>The <dfn id="attr-tabindex" title="attr-tabindex"><code>tabindex</code></dfn>
+  </div><h4 id="sequential-focus-navigation-and-the-tabindex-attribute"><span class="secno">7.3.1 </span>Sequential focus navigation and the <code title="attr-tabindex"><a href="#attr-tabindex">tabindex</a></code> attribute</h4><p>The <dfn id="attr-tabindex" title="attr-tabindex"><code>tabindex</code></dfn>
   content attribute specifies whether the element is focusable,
   whether it can be reached using sequential focus navigation, and the
   relative order of the element for the purposes of sequential focus
@@ -49746,7 +49703,7 @@
 
   </div><div class="impl">
 
-  <h4 id="focus-management"><span class="secno">7.4.2 </span>Focus management</h4>
+  <h4 id="focus-management"><span class="secno">7.3.2 </span>Focus management</h4>
 
   <p>An element is <dfn id="focusable">focusable</dfn> if the user agent's default
   behavior allows it to be focusable or if the element is
@@ -49844,7 +49801,7 @@
   element is removed from its <code><a href="#document">Document</a></code>, or has a <code title="attr-hidden"><a href="#the-hidden-attribute">hidden</a></code> attribute added. It would also
   happen to an <code><a href="#the-input-element">input</a></code> element when the element gets <a href="#concept-fe-disabled" title="concept-fe-disabled">disabled</a>.</p>
 
-  </div><h4 id="document-level-focus-apis"><span class="secno">7.4.3 </span>Document-level focus APIs</h4><dl class="domintro"><dt><var title="">document</var> . <code title="dom-document-activeElement"><a href="#dom-document-activeelement">activeElement</a></code></dt>
+  </div><h4 id="document-level-focus-apis"><span class="secno">7.3.3 </span>Document-level focus APIs</h4><dl class="domintro"><dt><var title="">document</var> . <code title="dom-document-activeElement"><a href="#dom-document-activeelement">activeElement</a></code></dt>
 
    <dd>
 
@@ -49914,7 +49871,7 @@
   system focus, but hostile sites widely abuse this behavior to the
   user's detriment.</p>
 
-  </div><h4 id="element-level-focus-apis"><span class="secno">7.4.4 </span>Element-level focus APIs</h4><dl class="domintro"><dt><var title="">element</var> . <code title="dom-focus"><a href="#dom-focus">focus</a></code>()</dt>
+  </div><h4 id="element-level-focus-apis"><span class="secno">7.3.4 </span>Element-level focus APIs</h4><dl class="domintro"><dt><var title="">element</var> . <code title="dom-focus"><a href="#dom-focus">focus</a></code>()</dt>
 
    <dd>
 
@@ -49973,7 +49930,7 @@
   unusable by keyboard users. Ignoring calls to this method would thus
   allow keyboard users to interact with the page.</p>
 
-  </div><h3 id="assigning-keyboard-shortcuts"><span class="secno">7.5 </span>Assigning keyboard shortcuts</h3><h4 id="introduction-5"><span class="secno">7.5.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>Each element that can be activated or focused can be assigned a
+  </div><h3 id="assigning-keyboard-shortcuts"><span class="secno">7.4 </span>Assigning keyboard shortcuts</h3><h4 id="introduction-5"><span class="secno">7.4.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>Each element that can be activated or focused can be assigned a
   single key combination to activate it, using the <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> attribute.<p>The exact shortcut is determined by the user agent, based on
   information about the user's keyboard, what keyboard shortcuts
   already exist on the platform, and what other shortcuts have been
@@ -49984,7 +49941,7 @@
   or digit.<p>User agents can provide users with a list of the keyboard
   shortcuts, but authors are encouraged to do so also. The <code title="dom-accessKeyLabel"><a href="#dom-accesskeylabel">accessKeyLabel</a></code> IDL attribute
   returns a string representing the actual key combination assigned by
-  the user agent.<h4 id="the-accesskey-attribute"><span class="secno">7.5.2 </span>The <dfn title="attr-accesskey"><code>accesskey</code></dfn> attribute</h4><p>All <a href="#html-elements">HTML elements</a> may have the <code title="attr-accesskey"><a href="#the-accesskey-attribute">accesskey</a></code> content attribute set. The
+  the user agent.<h4 id="the-accesskey-attribute"><span class="secno">7.4.2 </span>The <dfn title="attr-accesskey"><code>accesskey</code></dfn> attribute</h4><p>All <a href="#html-elements">HTML elements</a> 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
@@ -50049,7 +50006,7 @@
 
   </div><div class="impl">
 
-  <h4 id="processing-model-3"><span class="secno">7.5.3 </span>Processing model</h4>
+  <h4 id="processing-model-3"><span class="secno">7.4.3 </span>Processing model</h4>
 
   <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
@@ -50115,7 +50072,7 @@
   <a href="#assigned-access-key">assigned access key</a>, if any. If the element does not
   have one, then the IDL attribute must return the empty string.</p>
 
-  </div><h3 id="contenteditable"><span class="secno">7.6 </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>
+  </div><h3 id="contenteditable"><span class="secno">7.5 </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
@@ -50209,7 +50166,7 @@
 
   </div><div class="impl">
 
-  <h4 id="user-editing-actions"><span class="secno">7.6.1 </span>User editing actions</h4>
+  <h4 id="user-editing-actions"><span class="secno">7.5.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
@@ -50394,7 +50351,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">7.6.2 </span>Making entire documents editable</h4><div class="impl">
+  </div><h4 id="making-entire-documents-editable"><span class="secno">7.5.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>
@@ -50428,7 +50385,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">7.7 </span>Spelling and grammar checking</h3><div class="impl">
+  </div><h3 id="spelling-and-grammar-checking"><span class="secno">7.6 </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
@@ -50605,7 +50562,7 @@
   </div><p class="note">This specification does not define the user
   interface for spelling and grammar checkers. A user agent could
   offer on-demand checking, could perform continuous checking while
-  the checking is enabled, or could use other interfaces.<h3 id="dnd"><span class="secno">7.8 </span><dfn>Drag and drop</dfn></h3><!-- v2 ideas for drag and drop:
+  the checking is enabled, or could use other interfaces.<h3 id="dnd"><span class="secno">7.7 </span><dfn>Drag and drop</dfn></h3><!-- v2 ideas for drag and drop:
 
      * being able to animate a drop target:
 
@@ -50693,7 +50650,7 @@
   before the drop occurs (so if the operation is not canceled, there
   must be at least one element in the middle step).</p>
 
-  </div><h4 id="introduction-6"><span class="secno">7.8.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>To make an element draggable is simple: give the element a <code title="attr-draggable"><a href="#the-draggable-attribute">draggable</a></code> attribute, and set an event
+  </div><h4 id="introduction-6"><span class="secno">7.7.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>To make an element draggable is simple: give the element a <code title="attr-draggable"><a href="#the-draggable-attribute">draggable</a></code> attribute, and set an event
   listener for <code title="event-dragstart"><a href="#event-dragstart">dragstart</a></code> that
   stores the data being dragged.<p>The event handler typically needs to check that it's not a text
   selection that is being dragged, and then needs to store data into
@@ -50775,7 +50732,7 @@
     // remove the dragged element
     event.target.parentNode.removeChild(event.target);
   }
-&lt;/script&gt;</pre><h4 id="the-dragevent-and-datatransfer-interfaces"><span class="secno">7.8.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
+&lt;/script&gt;</pre><h4 id="the-dragevent-and-datatransfer-interfaces"><span class="secno">7.7.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> : <span>MouseEvent</span> {
   readonly attribute <a href="#datatransfer">DataTransfer</a> <a href="#dom-dragevent-datatransfer" title="dom-DragEvent-dataTransfer">dataTransfer</a>;
 
@@ -51012,7 +50969,7 @@
   current rendering of the elements added, whereas the former uses the
   exact specified image.</p>
 
-  </div><h4 id="dndevents"><span class="secno">7.8.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="dndevents"><span class="secno">7.7.3 </span>Events fired during a drag-and-drop action</h4><p>The following events are involved in the drag-and-drop
   model.<div class="impl">
 
   <p>Whenever the processing model described below causes one of these
@@ -51140,7 +51097,7 @@
     <td><code title="">copy</code></td>
    </table></div><div class="impl">
 
-  <h4 id="drag-and-drop-processing-model"><span class="secno">7.8.4 </span>Drag-and-drop processing model</h4>
+  <h4 id="drag-and-drop-processing-model"><span class="secno">7.7.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
@@ -51648,7 +51605,7 @@
 
   </div><div class="impl">
 
-  <h5 id="when-the-drag-and-drop-operation-starts-or-ends-in-another-document"><span class="secno">7.8.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">7.7.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
@@ -51659,7 +51616,7 @@
 
   </div><div class="impl">
 
-  <h5 id="when-the-drag-and-drop-operation-starts-or-ends-in-another-application"><span class="secno">7.8.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">7.7.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
@@ -51686,7 +51643,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">7.8.5 </span>The <dfn title="attr-draggable"><code>draggable</code></dfn> attribute</h4><p>All <a href="#html-elements">HTML elements</a> 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">7.7.5 </span>The <dfn title="attr-draggable"><code>draggable</code></dfn> attribute</h4><p>All <a href="#html-elements">HTML elements</a> 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
@@ -51816,7 +51773,7 @@
   </div>
 --><div class="impl">
 
-  <h4 id="security-risks-in-the-drag-and-drop-model"><span class="secno">7.8.6 </span>Security risks in the drag-and-drop model</h4>
+  <h4 id="security-risks-in-the-drag-and-drop-model"><span class="secno">7.7.6 </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
@@ -51839,9 +51796,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">7.9 </span><dfn>Undo history</dfn></h3><div class="impl">
+  </div><h3 id="undo"><span class="secno">7.8 </span><dfn>Undo history</dfn></h3><div class="impl">
 
-  <h4 id="definitions-2"><span class="secno">7.9.1 </span>Definitions</h4>
+  <h4 id="definitions-2"><span class="secno">7.8.1 </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>
@@ -51876,7 +51833,7 @@
   to higher-level user actions (such as interactions with server-side
   state, or in the implementation of a drawing tool).</p>
 
-  </div><h4 id="the-undomanager-interface"><span class="secno">7.9.2 </span>The <code><a href="#undomanager">UndoManager</a></code> interface</h4><p>To manage <a href="#undo-object">undo object</a> entries in the <a href="#undo-transaction-history">undo
+  </div><h4 id="the-undomanager-interface"><span class="secno">7.8.2 </span>The <code><a href="#undomanager">UndoManager</a></code> interface</h4><p>To manage <a href="#undo-object">undo object</a> entries in the <a href="#undo-transaction-history">undo
   transaction history</a>, the <code><a href="#undomanager">UndoManager</a></code>
   interface can be used:<pre class="idl">interface <dfn id="undomanager">UndoManager</dfn> {
   readonly attribute unsigned long <a href="#dom-undomanager-length" title="dom-UndoManager-length">length</a>;
@@ -52034,7 +51991,7 @@
 
   </div><div class="impl">
 
-  <h4 id="undo:-moving-back-in-the-undo-transaction-history"><span class="secno">7.9.3 </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">7.8.3 </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
@@ -52071,7 +52028,7 @@
   command to undo his undo.</p>
 
 
-  <h4 id="redo:-moving-forward-in-the-undo-transaction-history"><span class="secno">7.9.4 </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">7.8.4 </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
@@ -52105,7 +52062,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">7.9.5 </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> : <a href="#event">Event</a> {
+  </div><h4 id="the-undomanagerevent-interface-and-the-undo-and-redo-events"><span class="secno">7.8.5 </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> : <a href="#event">Event</a> {
   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);
 };</pre><dl class="domintro"><dt><var title="">event</var>  . <code title="dom-UndoManagerEvent-data"><a href="#dom-undomanagerevent-data">data</a></code></dt>
@@ -52133,7 +52090,7 @@
 
   </div><div class="impl">
 
-  <h4 id="implementation-notes"><span class="secno">7.9.6 </span>Implementation notes</h4>
+  <h4 id="implementation-notes"><span class="secno">7.8.6 </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
@@ -52150,7 +52107,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">7.10 </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">7.9 </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>
 
@@ -68472,6 +68429,10 @@
    <dd><cite><a href="http://dev.w3.org/csswg/cssom/">Cascading Style Sheets
    Object Model (CSSOM)</a></cite>, A. van Kesteren. W3C.</dd>
 
+   <dt id="refsCSSOMVIEW">[CSSOMVIEW]</dt>
+   <dd><cite><a href="http://dev.w3.org/csswg/cssom-view/">CSSOM View
+   Module</a></cite>, A. van Kesteren. W3C.</dd>
+
    <dt id="refsCSSRUBY">[CSSRUBY]</dt>
    <dd><cite><a href="http://dev.w3.org/csswg/css3-ruby/">CSS3 Ruby
    Module</a></cite>, R. Ishida. W3C.</dd>
Received on Wednesday, 13 October 2010 20:19:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 October 2010 20:19:15 GMT