hixie: Tidy up some XXX markers. (whatwg r3888)

hixie: Tidy up some XXX markers. (whatwg r3888)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3050&r2=1.3051&f=h
http://html5.org/tools/web-apps-tracker?from=3887&to=3888

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3050
retrieving revision 1.3051
diff -u -d -r1.3050 -r1.3051
--- Overview.html 18 Sep 2009 05:00:12 -0000 1.3050
+++ Overview.html 18 Sep 2009 05:06:40 -0000 1.3051
@@ -51303,7 +51303,7 @@
   as defined for the <code>Range</code> interface; this can therefore
   result in the members of the <code><a href="#selection-0">Selection</a></code> interface
   raising exceptions as well, in addition to any explicitly called out
-  below.</p><!-- XXX example --><dl class="domintro"><dt><var title="">selection</var> . <code title="dom-selection-anchorNode"><a href="#dom-selection-anchornode">anchorNode</a></code></dt>
+  below.<dl class="domintro"><dt><var title="">selection</var> . <code title="dom-selection-anchorNode"><a href="#dom-selection-anchornode">anchorNode</a></code></dt>
 
    <dd>
 
@@ -51515,8 +51515,7 @@
   range). Duplicates are not prevented; a range may be added more than
   once in which case it appears in the list more than once, which (for
   example) will cause <a href="#dom-selection-tostring" title="dom-selection-toString">stringification</a> to return the
-  range's text twice.</p> <!-- XXX how does this interact with
-  deleteFromDocument() which acts on all ranges? -->
+  range's text twice.</p>
 
   <p>The <dfn id="dom-selection-removerange" title="dom-selection-removeRange"><code>removeRange(<var title="">range</var>)</code></dfn>
   method must remove the first occurrence of <var title="">range</var> in the
@@ -51549,7 +51548,7 @@
   text selection:<pre class="idl extract">  void <a href="#dom-textarea-input-select" title="dom-textarea/input-select">select</a>();
            attribute unsigned long <a href="#dom-textarea-input-selectionstart" title="dom-textarea/input-selectionStart">selectionStart</a>;
            attribute unsigned long <a href="#dom-textarea-input-selectionend" title="dom-textarea/input-selectionEnd">selectionEnd</a>;
-  void <a href="#dom-textarea-input-setselectionrange" title="dom-textarea/input-setSelectionRange">setSelectionRange</a>(in unsigned long start, in unsigned long end);</pre><!-- XXX also add textLength? it seems to be widely used --><p>These methods and attributes expose and control the selection of
+  void <a href="#dom-textarea-input-setselectionrange" title="dom-textarea/input-setSelectionRange">setSelectionRange</a>(in unsigned long start, in unsigned long end);</pre><!-- v2: also add textLength? it seems to be widely used --><p>These methods and attributes expose and control the selection of
   <code><a href="#the-input-element">input</a></code> and <code><a href="#the-textarea-element">textarea</a></code> text fields.<dl class="domintro"><dt><var title="">element</var> . <code title="dom-textarea/input-select"><a href="#dom-textarea-input-select">select</a></code>()</dt>
 
    <dd>
@@ -51733,12 +51732,12 @@
   <p>When an editing host has focus, it must have a <dfn id="caret-position">caret
   position</dfn> that specifies where the current editing position
   is. It may also have a <a href="#the-selection" title="the
-  selection">selection</a>.</p> <!-- XXX xref to later section -->
+  selection">selection</a>.</p>
 
   <p class="note">How the caret and selection are represented depends
   entirely on the UA.</p>
 
-  <!-- XXX would be useful to have a way to mark an element as
+  <!-- v2: would be useful to have a way to mark an element as
   unremovable. -->
 
   </div><div class="impl">
@@ -51913,14 +51912,17 @@
    attribute. (Updating the <code title="">default*</code> IDL
    attributes causes content attributes to be updated as well.)</dd>
 
-   <!-- XXX something about not supporting resizing? -->
-
-  </dl><!-- XXX each action performed should be added to the undo history --><p>User agents may perform several commands per user request; for
+  </dl><p>User agents may perform several commands per user request; for
   example if the user selects a block of text and hits
   <kbd><kbd>Enter</kbd></kbd>, the UA might interpret that as a
   request to delete the content of <a href="#the-selection">the selection</a> followed
   by a request to break the paragraph at that position.</p>
 
+  <p>User agents may add <a href="#dom-changes">DOM changes</a> entries to the
+  <a href="#undo-transaction-history">undo transaction history</a> of the <a href="#editing-host">editing
+  host</a>'s <code>Document</code> object each time an action is
+  triggered.</p>
+
   <p>All of the actions defined above, whether triggered by the user
   or programmatically (e.g. by <code title="dom-document-execCommand"><a href="#execCommand">execCommand()</a></code> commands),
   must fire mutation events as appropriate.</p>

Received on Friday, 18 September 2009 05:07:39 UTC