- From: poot <cvsmail@w3.org>
- Date: Tue, 11 Jan 2011 21:44:18 -0500
- To: public-html-diffs@w3.org
hixie: Remove UndoManager from W3C HTML5 spec since it's not really
fully baked yet. (whatwg r5735)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4597&r2=1.4598&f=h
http://html5.org/tools/web-apps-tracker?from=5734&to=5735
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4597
retrieving revision 1.4598
diff -u -d -r1.4597 -r1.4598
--- Overview.html 1 Jan 2011 05:59:03 -0000 1.4597
+++ Overview.html 1 Jan 2011 06:20:58 -0000 1.4598
@@ -1155,15 +1155,7 @@
<li><a href="#the-draggable-attribute"><span class="secno">7.7.7 </span>The <code>draggable</code> attribute</a></li>
<li><a href="#the-dropzone-attribute"><span class="secno">7.7.8 </span>The <code>dropzone</code> attribute</a></li>
<li><a href="#security-risks-in-the-drag-and-drop-model"><span class="secno">7.7.9 </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.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="#editing-apis"><span class="secno">7.8 </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>
@@ -10336,13 +10328,13 @@
<li><p>Replace the <code><a href="#document">Document</a></code>'s singleton objects with
new instances of those objects. (This includes in particular the
<code><a href="#window">Window</a></code>, <code><a href="#location">Location</a></code>, <code><a href="#history-0">History</a></code>,
- <code><a href="#applicationcache">ApplicationCache</a></code>, <code><a href="#undomanager">UndoManager</a></code>, and
- <code><a href="#navigator">Navigator</a></code>, objects, the various <code><a href="#barprop">BarProp</a></code>
- objects, the two <code>Storage</code> objects, the various
- <code><a href="#htmlcollection">HTMLCollection</a></code> objects, and objects defined by other
- specifications, like <code>Selection</code>. It also includes all
- the Web IDL prototypes in the JavaScript binding, including the
- <code><a href="#document">Document</a></code> object's prototype.)</li>
+ <code><a href="#applicationcache">ApplicationCache</a></code>,
+ and <code><a href="#navigator">Navigator</a></code>, objects, the various
+ <code><a href="#barprop">BarProp</a></code> objects, the two <code>Storage</code> objects,
+ the various <code><a href="#htmlcollection">HTMLCollection</a></code> objects, and objects
+ defined by other specifications, like <code>Selection</code>. It
+ also includes all the Web IDL prototypes in the JavaScript binding,
+ including the <code><a href="#document">Document</a></code> object's prototype.)</li>
<!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E...%3Ciframe%20src%3D%22document%22%3E%3C%2Fiframe%3E%0A%3Cscript%3Eonload%20%3D%20function%20()%20%7B%20f%20%3D%20document.getElementsByTagName('iframe')%5B0%5D%3B%20d%20%3D%20f.contentWindow.document%3B%20%7D%3C%2Fscript%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22w(d.documentElement.innerHTML)%22%20value%3D%22dump%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cscript%3Evar%20x%20%3D%20new%20XMLHttpRequest()%3Bx.open(%26quot%3BGET%26quot%3B%2C%20%26quot%3BGET%26quot%3B)%3Bx.onreadystatechange%3Dfunction()%20%7B%20alert(x.readyState)%3B%20%7D%3Bx.send(null)%3B%3C%2Fscript%3E')%3Bd.close()%3B%20setTimeout(function()%20%7B%20d.open()%3B%20d.write('%3Cp%3Etest%3C%2Fp%3E')%3B%20d.close()%20%7D%2C%200)%3B%22%20value%3D%22xhr%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.onclick%20%3D%20function()%20%7B%20w('click')%20%7D%22%20value%3D%22add%20click%20handler%22%3E%0A%3Cinput%20type%3Dbutton%20oncick%3D%22d.open()%3B%20d.write('%3Cp%3Etest%3C%2Fp%3E')%3B%20d.close()%22%20value%3D%22replace%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cp%3E%3Cscript%3Ei%20%3D%200%3B%20setTimeout(%26quot%3Bparent.w(i%2B%2B)%26quot%3B%2C%202000)%3C%2Fscript%3E%3C%2Fp%3E')%3B%20d.close()%22%20value%3D%22replace%20with%20timer%22%3E -->
<!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0D%0A...%3Ciframe%3E%3C%2Fiframe%3E%0D%0A%3Cscript%3E%0D%0Aonload%20%3D%20function%20()%20%7B%0D%0A%20frames%5B0%5D.test%20%3D%201%0D%0A%20w(frames%5B0%5D.test)%3B%0D%0A%20var%20a%20%3D%20frames%5B0%5D.document.location.assign%3B%0D%0A%20w(a)%3B%0D%0A%20w(frames%5B0%5D.document.location.assign%20%3D%3D%3D%20a)%3B%0D%0A%20frames%5B0%5D.document.open()%3B%0D%0A%20frames%5B0%5D.document.write('%3Cscript%3Edocument.write(test)%3C%5C%2Fscript%3E')%3B%0D%0A%20frames%5B0%5D.document.close()%3B%0D%0A%20w(frames%5B0%5D.test)%3B%0D%0A%20w(frames%5B0%5D.document.location.assign%20%3D%3D%3D%20a)%3B%0D%0A%7D%0D%0A%3C%2Fscript%3E -->
@@ -41826,7 +41818,6 @@
attribute DOMString <a href="#dom-name" title="dom-name">name</a>; <!-- not [Replaceable] per WebKit and IE8 -->
[PutForwards=<a href="#dom-location-href" title="dom-location-href">href</a>] readonly attribute <a href="#location">Location</a> <a href="#dom-location" title="dom-location">location</a>;
readonly attribute <a href="#history-0">History</a> <a href="#dom-history" title="dom-history">history</a>;
- readonly attribute <a href="#undomanager">UndoManager</a> <a href="#dom-undomanager" title="dom-undoManager">undoManager</a>;
[Replaceable] readonly attribute <a href="#barprop">BarProp</a> <a href="#dom-window-locationbar" title="dom-window-locationbar">locationbar</a>;
[Replaceable] readonly attribute <a href="#barprop">BarProp</a> <a href="#dom-window-menubar" title="dom-window-menubar">menubar</a>;
[Replaceable] readonly attribute <a href="#barprop">BarProp</a> <a href="#dom-window-personalbar" title="dom-window-personalbar">personalbar</a>;
@@ -48050,11 +48041,11 @@
<tr><td><dfn id="handler-window-onpagehide" title="handler-window-onpagehide"><code>onpagehide</code></dfn> <td> <code title="event-pagehide"><a href="#event-pagehide">pagehide</a></code> <!-- new -->
<tr><td><dfn id="handler-window-onpageshow" title="handler-window-onpageshow"><code>onpageshow</code></dfn> <td> <code title="event-pageshow"><a href="#event-pageshow">pageshow</a></code> <!-- new -->
<tr><td><dfn id="handler-window-onpopstate" title="handler-window-onpopstate"><code>onpopstate</code></dfn> <td> <code title="event-popstate"><a href="#event-popstate">popstate</a></code> <!-- new -->
- <tr><td><dfn id="handler-window-onredo" title="handler-window-onredo"><code>onredo</code></dfn> <td> <code title="event-redo"><a href="#event-redo">redo</a></code> <!-- new -->
+ <tr><td><dfn id="handler-window-onredo" title="handler-window-onredo"><code>onredo</code></dfn> <td> <code title="event-redo">redo</code> <!-- new -->
<tr><td><dfn id="handler-window-onresize" title="handler-window-onresize"><code>onresize</code></dfn> <td> <code title="event-resize">resize</code> <!-- widely used --> <!-- [CSSOM] -->
<tr><td><dfn id="handler-window-onscroll" title="handler-window-onscroll"><code>onscroll</code></dfn> <td> <code title="event-scroll">scroll</code>
<tr><td><dfn id="handler-window-onstorage" title="handler-window-onstorage"><code>onstorage</code></dfn> <td> <code title="event-storage">storage</code> <!-- new -->
- <tr><td><dfn id="handler-window-onundo" title="handler-window-onundo"><code>onundo</code></dfn> <td> <code title="event-undo"><a href="#event-undo">undo</a></code> <!-- new -->
+ <tr><td><dfn id="handler-window-onundo" title="handler-window-onundo"><code>onundo</code></dfn> <td> <code title="event-undo">undo</code> <!-- new -->
<tr><td><dfn id="handler-window-onunload" title="handler-window-onunload"><code>onunload</code></dfn> <td> <code title="event-unload">unload</code> <!-- widely used -->
</table><p class="note">The <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code>
handler is also used for <a href="#runtime-script-errors">reporting script errors</a>.</p>
@@ -50183,8 +50174,8 @@
request to delete the content of the selection 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
+ <p>User agents may add <span>DOM changes</span> entries to the
+ <span>undo transaction history</span> of the <a href="#editing-host">editing
host</a>'s <code><a href="#document">Document</a></code> object each time an action is
triggered.</p>
@@ -51812,8 +51803,8 @@
operation, device input events (e.g. mouse and keyboard events) must
be suppressed. In addition, the user agent must track all DOM
changes made during the drag-and-drop operation, and add them to its
- <a href="#undo">undo history</a> as one atomic operation once the
- drag-and-drop operation has ended.</p>
+ <span>undo transaction history</span> as one atomic operation once
+ the drag-and-drop operation has ended.</p>
<p>During the drag operation, the element directly indicated by the
user as the drop target is called the <dfn id="immediate-user-selection">immediate user
@@ -52644,318 +52635,7 @@
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.8 </span><dfn>Undo history</dfn></h3><div class="impl">
-
- <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="#document">Document</a></code> object.</p>
-
- <p>The <a href="#undo-transaction-history">undo transaction history</a> is a list of
- entries. The entries are of two types: <a href="#dom-changes">DOM changes</a> and
- <a href="#undo-object" title="undo object">undo objects</a>.</p>
-
- <p>Each <dfn id="dom-changes">DOM changes</dfn> entry in the <a href="#undo-transaction-history">undo transaction
- history</a> consists of batches of one or more of the
- following:</p>
-
- <ul><li>Changes to the content attributes of an <code><a href="#element">Element</a></code>
- node.</li>
-
- <li>Changes to the DOM hierarchy of nodes that are descendants of
- the <code><a href="#document">Document</a></code> object (<code title="dom-Node-parentNode"><a href="#dom-node-parentnode">parentNode</a></code>, <code title="dom-Node-childNodes"><a href="#dom-node-childnodes">childNodes</a></code>).</li>
-
- <li>Changes to internal state, such as a form control's <a href="#concept-fe-value" title="concept-fe-value">value</a> or <a href="#concept-input-checked-dirty-flag" title="concept-input-checked-dirty-flag">dirty checkedness
- flag</a>.</li>
-
- </ul><p><dfn id="undo-object">Undo object</dfn> entries consist of objects representing
- state that scripts running in the document are managing. For
- example, a Web mail application could use an <a href="#undo-object">undo
- object</a> to keep track of the fact that a user has moved an
- e-mail to a particular folder, so that the user can undo the
- action and have the e-mail return to its former location.</p>
-
- <p>Broadly speaking, <a href="#dom-changes">DOM changes</a> entries are handled by
- the UA in response to user edits of form controls and <a href="#editing-host" title="editing host">editing hosts</a> on the page, and
- <a href="#undo-object">undo object</a> entries are handled by script in response
- 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.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>;
- getter any <a href="#dom-undomanager-item" title="dom-UndoManager-item">item</a>(in unsigned long index);
- readonly attribute unsigned long <a href="#dom-undomanager-position" title="dom-UndoManager-position">position</a>;
- unsigned long <a href="#dom-undomanager-add" title="dom-UndoManager-add">add</a>(in any data, in DOMString title);
- void <a href="#dom-undomanager-remove" title="dom-UndoManager-remove">remove</a>(in unsigned long index);
- void <a href="#dom-undomanager-clearundo" title="dom-UndoManager-clearUndo">clearUndo</a>();
- void <a href="#dom-undomanager-clearredo" title="dom-UndoManager-clearRedo">clearRedo</a>();
-};</pre><dl class="domintro"><dt><var title="">window</var> . <code title="dom-undoManager"><a href="#dom-undomanager">undoManager</a></code></dt>
-
- <dd>
-
- <p>Returns the <code><a href="#undomanager">UndoManager</a></code> object.</p>
-
- </dd>
-
- <dt><var title="">undoManager</var> . <code title="dom-UndoManager-length"><a href="#dom-undomanager-length">length</a></code></dt>
- <dd>
-
- <p>Returns the number of entries in the undo history.</p>
-
- </dd>
-
- <dt><var title="">data</var> = <var title="">undoManager</var> . <code title="dom-UndoManager-item"><a href="#dom-undomanager-item">item</a></code>(<var title="">index</var>)</dt>
- <dt><var title="">undoManager</var>[<var title="">index</var>]</dt>
- <dd>
-
- <p>Returns the entry with index <var title="">index</var> in the undo history.</p>
-
- <p>Returns null if <var title="">index</var> is out of range.</p>
-
- </dd>
-
- <dt><var title="">undoManager</var> . <code title="dom-UndoManager-position"><a href="#dom-undomanager-position">position</a></code></dt>
- <dd>
-
- <p>Returns the number of the current entry in the undo history. (Entries at and past this point are <em>redo</em> entries.)</p>
-
- </dd>
-
- <dt><var title="">undoManager</var> . <code title="dom-UndoManager-add"><a href="#dom-undomanager-add">add</a></code>(<var title="">data</var>, <var title="">title</var>)</dt>
- <dd>
-
- <p>Adds the specified entry to the undo history.</p>
-
- </dd>
-
- <dt><var title="">undoManager</var> . <code title="dom-UndoManager-remove"><a href="#dom-undomanager-remove">remove</a></code>(<var title="">index</var>)</dt>
- <dd>
-
- <p>Removes the specified entry to the undo history.</p>
-
- <p>Throws an <code><a href="#index_size_err">INDEX_SIZE_ERR</a></code> exception if the given index is out of range.</p>
-
- </dd>
-
- <dt><var title="">undoManager</var> . <code title="dom-UndoManager-clearUndo"><a href="#dom-undomanager-clearundo">clearUndo</a></code>()</dt>
- <dd>
-
- <p>Removes all entries before the current position in the undo history.</p>
-
- </dd>
-
- <dt><var title="">undoManager</var> . <code title="dom-UndoManager-clearRedo"><a href="#dom-undomanager-clearredo">clearRedo</a></code>()</dt>
- <dd>
-
- <p>Removes all entries at and after the current position in the undo history.</p>
-
- </dd>
-
- </dl><div class="impl">
-
- <p>The <dfn id="dom-undomanager" title="dom-undoManager"><code>undoManager</code></dfn>
- attribute of the <code><a href="#window">Window</a></code> interface must return the
- object implementing the <code><a href="#undomanager">UndoManager</a></code> interface for that
- <code><a href="#window">Window</a></code> object's associated <code><a href="#document">Document</a></code>
- object.</p>
-
- <p><code><a href="#undomanager">UndoManager</a></code> objects represent their document's
- <a href="#undo-transaction-history">undo transaction history</a>. Only <a href="#undo-object">undo object</a>
- entries are visible with this API, but this does not mean that
- <a href="#dom-changes">DOM changes</a> entries are absent from the <a href="#undo-transaction-history">undo
- transaction history</a>.</p>
-
- <p>The <dfn id="dom-undomanager-length" title="dom-UndoManager-length"><code>length</code></dfn>
- attribute must return the number of <a href="#undo-object">undo object</a> entries
- in the <a href="#undo-transaction-history">undo transaction history</a>. This is the <var title="dom-UndoManager-length"><a href="#dom-undomanager-length">length</a></var>.</p>
-
- <p>The object's <a href="#supported-property-indices">supported property indices</a> are the
- numbers in the range zero to <span title=""><var title="dom-UndoManager-length"><a href="#dom-undomanager-length">length</a></var>-1</span>, unless the
- <var title="dom-UndoManager-length"><a href="#dom-undomanager-length">length</a></var> is zero, in which
- case there are no <a href="#supported-property-indices">supported property indices</a>.</p>
-
- <p>The <dfn id="dom-undomanager-item" title="dom-UndoManager-item"><code>item(<var title="">n</var>)</code></dfn> method must return the <var title="">n</var>th <a href="#undo-object">undo object</a> entry in the <a href="#undo-transaction-history">undo
- transaction history</a>, if there is one, or null otherwise.</p>
-
- <p>The <a href="#undo-transaction-history">undo transaction history</a> has an <dfn id="undo-position">undo
- position</dfn>. This is the position between two entries in the
- <a href="#undo-transaction-history">undo transaction history</a>'s list where the previous
- entry represents what needs to happen if the user invokes the "undo"
- command (the "undo" side, lower numbers), and the next entry
- represents what needs to happen if the user invokes the "redo"
- command (the "redo" side, higher numbers).</p>
-
- <p>The <dfn id="dom-undomanager-position" title="dom-UndoManager-position"><code>position</code></dfn>
- attribute must return the index of the <a href="#undo-object">undo object</a>
- entry nearest to the <a href="#undo-position">undo position</a>, on the "redo"
- side. If there are no <a href="#undo-object">undo object</a> entries on the "redo"
- side, then the attribute must return the same as the <code title="dom-UndoManager-length"><a href="#dom-undomanager-length">length</a></code> attribute. If there are
- no <a href="#undo-object">undo object</a> entries on the "undo" side of the
- <a href="#undo-position">undo position</a>, the <code title="dom-UndoManager-position"><a href="#dom-undomanager-position">position</a></code> attribute returns
- zero.</p>
-
- <p class="note">Since the <a href="#undo-transaction-history">undo transaction history</a>
- contains both <a href="#undo-object">undo object</a> entries and <a href="#dom-changes">DOM
- changes</a> entries, but the <code title="dom-UndoManager-position"><a href="#dom-undomanager-position">position</a></code> attribute only
- returns indices relative to <a href="#undo-object">undo object</a> entries, it is
- possible for several "undo" or "redo" actions to be performed
- without the value of the <code title="dom-UndoManager-position"><a href="#dom-undomanager-position">position</a></code> attribute
- changing.</p>
-
- <p>The <dfn id="dom-undomanager-add" title="dom-UndoManager-add"><code>add(<var title="">data</var>,
- <var title="">title</var>)</code></dfn> method's behavior depends on the
- current state. Normally, it must insert the <var title="">data</var> object
- passed as an argument into the <a href="#undo-transaction-history">undo transaction history</a>
- immediately before the <a href="#undo-position">undo position</a>, optionally
- remembering the given <var title="">title</var> to use in the UI. If the
- method is called <a href="#undo:-moving-back-in-the-undo-transaction-history" title="do-undo">during an undo
- operation</a>, however, the object must instead be added
- immediately <em>after</em> the <a href="#undo-position">undo position</a>.</p>
-
- <p>If the method is called and there is neither <a href="#undo:-moving-back-in-the-undo-transaction-history" title="do-undo">an undo operation in progress</a> nor <a href="#redo:-moving-forward-in-the-undo-transaction-history" title="do-redo">a redo operation in progress</a> then any entries
- in the <a href="#undo-transaction-history">undo transaction history</a> after the <a href="#undo-position">undo
- position</a> must be removed (as if <code title="dom-UndoManager-clearRedo"><a href="#dom-undomanager-clearredo">clearRedo()</a></code> had been
- called).</p>
-
- <p>The <dfn id="dom-undomanager-remove" title="dom-UndoManager-remove"><code>remove(<var title="">index</var>)</code></dfn> method must remove the <a href="#undo-object">undo
- object</a> entry with the specified <var title="">index</var>. If
- the index is less than zero or greater than or equal to <code title="dom-UndoManager-length"><a href="#dom-undomanager-length">length</a></code> then the method must
- raise an <code><a href="#index_size_err">INDEX_SIZE_ERR</a></code> exception. <a href="#dom-changes">DOM
- changes</a> entries are unaffected by this method.</p>
-
- <p>The <dfn id="dom-undomanager-clearundo" title="dom-UndoManager-clearUndo"><code>clearUndo()</code></dfn>
- method must remove all entries in the <a href="#undo-transaction-history">undo transaction
- history</a> before the <a href="#undo-position">undo position</a>, be they
- <a href="#dom-changes">DOM changes</a> entries or <a href="#undo-object">undo object</a>
- entries.</p>
-
- <p>The <dfn id="dom-undomanager-clearredo" title="dom-UndoManager-clearRedo"><code>clearRedo()</code></dfn>
- method must remove all entries in the <a href="#undo-transaction-history">undo transaction
- history</a> after the <a href="#undo-position">undo position</a>, be they
- <a href="#dom-changes">DOM changes</a> entries or <a href="#undo-object">undo object</a>
- entries.</p>
-
- </div><div class="impl">
-
- <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
- user agent must perform an undo operation.</p>
-
- <p>If the <a href="#undo-position">undo position</a> is at the start of the
- <a href="#undo-transaction-history">undo transaction history</a>, then the user agent must do
- nothing.</p>
-
- <p>If the entry immediately before the <a href="#undo-position">undo position</a> is
- a <a href="#dom-changes">DOM changes</a> entry, then the user agent must remove
- that <a href="#dom-changes">DOM changes</a> entry, reverse the DOM changes that
- were listed in that entry, and, if the changes were reversed with no
- problems, add a new <a href="#dom-changes">DOM changes</a> entry (consisting of
- the opposite of those DOM changes) to the <a href="#undo-transaction-history">undo transaction
- history</a> on the other side of the <a href="#undo-position">undo
- position</a>.</p>
-
- <p>If the DOM changes cannot be undone (e.g. because the DOM state
- is no longer consistent with the changes represented in the entry),
- then the user agent must simply remove the <a href="#dom-changes">DOM changes</a>
- entry, without doing anything else.</p>
-
- <p>If the entry immediately before the <a href="#undo-position">undo position</a> is
- an <a href="#undo-object">undo object</a> entry, then the user agent must first
- remove that <a href="#undo-object">undo object</a> entry from the <a href="#undo-transaction-history">undo
- transaction history</a>, and then must fire an <code title="event-undo"><a href="#event-undo">undo</a></code> event at the <code><a href="#window">Window</a></code>
- object, using the <a href="#undo-object">undo object</a> entry's associated undo
- object as the event's data.</p>
-
- <p>Any calls to <code title="dom-undoManager-add"><a href="#dom-undomanager-add">add()</a></code> while
- the event is being handled will be used to populate the redo
- history, and will then be used if the user invokes the "redo"
- command to undo his undo.</p>
-
-
- <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
- user agent must perform a redo operation.</p>
-
- <p>This is mostly the opposite of an <a href="#undo:-moving-back-in-the-undo-transaction-history" title="do-undo">undo
- operation</a>, but the full definition is included here for
- completeness.</p>
-
- <p>If the <a href="#undo-position">undo position</a> is at the end of the <a href="#undo-transaction-history">undo
- transaction history</a>, then the user agent must do nothing.</p>
-
- <p>If the entry immediately after the <a href="#undo-position">undo position</a> is
- a <a href="#dom-changes">DOM changes</a> entry, then the user agent must remove
- that <a href="#dom-changes">DOM changes</a> entry, reverse the DOM changes that
- were listed in that entry, and, if the changes were reversed with no
- problems, add a new <a href="#dom-changes">DOM changes</a> entry (consisting of
- the opposite of those DOM changes) to the <a href="#undo-transaction-history">undo transaction
- history</a> on the other side of the <a href="#undo-position">undo
- position</a>.</p>
-
- <p>If the DOM changes cannot be redone (e.g. because the DOM state
- is no longer consistent with the changes represented in the entry),
- then the user agent must simply remove the <a href="#dom-changes">DOM changes</a>
- entry, without doing anything else.</p>
-
- <p>If the entry immediately after the <a href="#undo-position">undo position</a> is
- an <a href="#undo-object">undo object</a> entry, then the user agent must first
- remove that <a href="#undo-object">undo object</a> entry from the <a href="#undo-transaction-history">undo
- transaction history</a>, and then must fire a <code title="event-redo"><a href="#event-redo">redo</a></code> event at the <code><a href="#window">Window</a></code>
- 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.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>
-
- <dd>
-
- <p>Returns the data that was passed to the <code title="dom-undomanager-add"><a href="#dom-undomanager-add">add()</a></code> method.</p>
-
- </dd>
-
- </dl><div class="impl">
-
- <p>The <dfn id="dom-undomanagerevent-initundomanagerevent" title="dom-UndoManagerEvent-initUndoManagerEvent"><code>initUndoManagerEvent()</code></dfn>
- method must initialize the event in a manner analogous to the
- similarly-named method in the DOM Events interfaces. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
-
- <p>The <dfn id="dom-undomanagerevent-data" title="dom-UndoManagerEvent-data"><code>data</code></dfn>
- attribute represents the <a href="#undo-object">undo object</a> for the event.</p>
-
- <p>The <dfn id="event-undo" title="event-undo"><code>undo</code></dfn> and <dfn id="event-redo" title="event-redo"><code>redo</code></dfn> events do not bubble,
- cannot be canceled, and have no default action. When the user agent
- fires one of these events it must use the
- <code><a href="#undomanagerevent">UndoManagerEvent</a></code> interface, with the <code title="dom-UndoManagerEvent-data"><a href="#dom-undomanagerevent-data">data</a></code> field containing the
- relevant <a href="#undo-object">undo object</a>.</p>
-
- </div><div class="impl">
-
- <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
- <a href="#undo-transaction-history">undo transaction history</a>, it could manipulate the
- <a href="#undo-transaction-history">undo transaction history</a> in ways not described above,
- and so forth. For example, it is possible to design a UA that
- appears to have separate <a href="#undo-transaction-history" title="undo transaction history">undo
- transaction histories</a> for each form control; similarly, it is
- possible to design systems where the user has access to more undo
- information than is present in the official (as described above)
- <a href="#undo-transaction-history">undo transaction history</a> (such as providing a
- tree-based approach to document state). Such UI models should be
- based upon the single <a href="#undo-transaction-history">undo transaction history</a>
- 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.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>
+ </div><h3 id="editing-apis"><span class="secno">7.8 </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>
@@ -53282,14 +52962,14 @@
<dt><dfn id="command-redo" title="command-redo"><code>redo</code></dfn></dt>
<dd><strong>Summary</strong>: Acts as if the user had requested a redo.</dd>
- <dd class="impl"><strong>Action</strong>: The user agent must <a href="#redo:-moving-forward-in-the-undo-transaction-history" title="do-redo">move forward one step</a> in its <a href="#undo-transaction-history">undo
- transaction history</a>, restoring the associated state. If the
- <a href="#undo-position">undo position</a> is at the end of the <a href="#undo-transaction-history">undo
- transaction history</a>, the user agent must do nothing. See the
- <a href="#undo">undo history</a>.</dd>
- <dd><strong>Enabled When</strong>: The <a href="#undo-position">undo position</a>
- is not at the end of the <a href="#undo-transaction-history">undo transaction
- history</a>.</dd>
+ <dd class="impl"><strong>Action</strong>: The user agent must <span title="do-redo">move forward one step</span> in its <span>undo
+ transaction history</span>, restoring the associated state. If the
+ <span>undo position</span> is at the end of the <span>undo
+ transaction history</span>, the user agent must do nothing.
+ </dd>
+ <dd><strong>Enabled When</strong>: The <span>undo position</span>
+ is not at the end of the <span>undo transaction
+ history</span>.</dd>
<dd><strong>Indeterminate When</strong>: Never.</dd>
<dd><strong>State</strong>: Always false.</dd>
<dd><strong>Value</strong>: Always the string "<code title="">false</code>".</dd>
@@ -53342,14 +53022,14 @@
<dt><dfn id="command-undo" title="command-undo"><code>undo</code></dfn></dt>
<dd><strong>Summary</strong>: Acts as if the user had requested an undo.</dd>
- <dd class="impl"><strong>Action</strong>: The user agent must <a href="#undo:-moving-back-in-the-undo-transaction-history" title="do-undo">move back one step</a> in its <a href="#undo-transaction-history">undo
- transaction history</a>, restoring the associated state. If the
- <a href="#undo-position">undo position</a> is at the start of the <a href="#undo-transaction-history">undo
- transaction history</a>, the user agent must do nothing. See the
- <a href="#undo">undo history</a>.</dd>
- <dd><strong>Enabled When</strong>: The <a href="#undo-position">undo position</a>
- is not at the start of the <a href="#undo-transaction-history">undo transaction
- history</a>.</dd>
+ <dd class="impl"><strong>Action</strong>: The user agent must <span title="do-undo">move back one step</span> in its <span>undo
+ transaction history</span>, restoring the associated state. If the
+ <span>undo position</span> is at the start of the <span>undo
+ transaction history</span>, the user agent must do nothing.
+ </dd>
+ <dd><strong>Enabled When</strong>: The <span>undo position</span>
+ is not at the start of the <span>undo transaction
+ history</span>.</dd>
<dd><strong>Indeterminate When</strong>: Never.</dd>
<dd><strong>State</strong>: Always false.</dd>
<dd><strong>Value</strong>: Always the string "<code title="">false</code>".</dd>
@@ -69896,7 +69576,7 @@
<tr><th id="ix-handler-window-onredo"> <code title="">onredo</code>
<td> <code title="handler-window-onredo"><a href="#handler-window-onredo">body</a></code>
- <td> <code title="event-redo"><a href="#event-redo">redo</a></code> event handler for <code><a href="#window">Window</a></code> object
+ <td> <code title="event-redo">redo</code> event handler for <code><a href="#window">Window</a></code> object
<td> <a href="#event-handler-content-attributes" title="event handler content attributes">Event handler content attribute</a>
<tr><th id="ix-handler-onreset"> <code title="">onreset</code>
@@ -69966,7 +69646,7 @@
<tr><th id="ix-handler-window-onundo"> <code title="">onundo</code>
<td> <code title="handler-window-onundo"><a href="#handler-window-onundo">body</a></code>
- <td> <code title="event-undo"><a href="#event-undo">undo</a></code> event handler for <code><a href="#window">Window</a></code> object
+ <td> <code title="event-undo">undo</code> event handler for <code><a href="#window">Window</a></code> object
<td> <a href="#event-handler-content-attributes" title="event handler content attributes">Event handler content attribute</a>
<tr><th id="ix-handler-window-onunload"> <code title="">onunload</code>
@@ -70425,9 +70105,6 @@
<td> <code><a href="#event">Event</a></code>
<td> Fired at the <code><a href="#document">Document</a></code> when it finishes parsing and again when all its subresources have finished loading
- <tr><td> <code title="event-redo"><a href="#event-redo">redo</a></code>
- <td> <code><a href="#undomanagerevent">UndoManagerEvent</a></code>
- <td> Fired at the <code><a href="#window">Window</a></code> object when the user <a href="#redo:-moving-forward-in-the-undo-transaction-history" title="do-redo">goes forward in the undo transaction history</a>
<tr><td> <code title="event-reset">reset</code>
<td> <code><a href="#event">Event</a></code>
@@ -70441,9 +70118,6 @@
<td> <code><a href="#event">Event</a></code>
<td> Fired at a <code><a href="#the-form-element">form</a></code> element when it is <a href="#concept-form-submit" title="concept-form-submit">submitted</a>
- <tr><td> <code title="event-undo"><a href="#event-undo">undo</a></code>
- <td> <code><a href="#undomanagerevent">UndoManagerEvent</a></code>
- <td> Fired at the <code><a href="#window">Window</a></code> object when the user <a href="#undo:-moving-back-in-the-undo-transaction-history" title="do-undo">goes backward in the undo transaction history</a>
<tr><td> <code title="event-unload">unload</code>
<td> <code><a href="#event">Event</a></code>
Received on Wednesday, 12 January 2011 02:44:21 UTC