Short URL: http://html5.org/r/6603
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 6603 | 13425 | Remove remaining editing section stuff as there are bugs tracking it. | 2011-09-30 00:30 |
Index: source =================================================================== --- source (revision 6602) +++ source (revision 6603) @@ -81860,91 +81860,6 @@ - <div class="impl"> - - <h4>User editing actions</h4> - - <p class="XXX">This section will be removed shortly. What remains - here is simply what has not yet been merged into Aryeh's spec.</p> - - <p>There are several actions that the user agent should allow the - user to perform while the user is interacting with an editing - host. How exactly each action is triggered is not defined for every - action, but when it is not defined, suggested key bindings are - provided to guide implementors.</p> - - <dl> - - <dt id="contenteditable-wrapSemantic">Insert, and wrap text in, - semantic elements</dt> - - <dd><p>UAs should offer the user the ability to mark text and - paragraphs with semantics that HTML can express.</p> - - <p>UAs should similarly offer a way for the user to insert empty - semantic elements to subsequently fill by entering text - manually.</p> - - <p>UAs should also offer a way to remove those semantics from - marked up text, and to remove empty semantic element that have been - inserted.</p> - - <p>In response to a request from a user to mark text up in italics, - user agents should use the <code>i</code> element to represent the - semantic. The <code>em</code> element should be used only if the - user agent is sure that the user means to indicate stress - emphasis.</p> - - <p>In response to a request from a user to mark text up in bold, - user agents should use the <code>b</code> element to represent the - semantic. The <code>strong</code> element should be used only if - the user agent is sure that the user means to indicate - importance.</p> - - <p>The exact behavior is UA-dependent, but user agents must not, - in response to a request to wrap semantics around some text or to - insert or remove a semantic element, generate a DOM that is less - conformant than the DOM prior to the request.</p></dd> - - - <dt>Select and move non-editable elements nested inside editing hosts</dt> - - <dd><p>UAs should offer a way for the user to move images and other - non-editable parts around the content within an editing host. This - may be done using the <span>drag and drop</span> mechanism. User - agents must not, in response to a request to move non-editable - elements nested inside editing hosts, generate a DOM that is less - conformant than the DOM prior to the request.</p></dd> - - - <dt>Edit form controls nested inside editing hosts</dt> - - <dd><p>When an <span>editable</span> form control is edited, the - changes must be reflected in both its current value <em>and</em> - its default value. For <code>input</code> elements this means - updating the <code - title="dom-input-defaultValue">defaultValue</code> IDL attribute as - well as the <code title="dom-input-value">value</code> IDL - attribute; for <code>select</code> elements it means updating the - <code>option</code> elements' <code - title="dom-option-defaultSelected">defaultSelected</code> IDL - attribute as well as the <code - title="dom-option-selected">selected</code> IDL attribute; for - <code>textarea</code> elements this means updating the <code - title="dom-textarea-defaultValue">defaultValue</code> IDL attribute - as well as the <code title="dom-textarea-value">value</code> IDL - attribute. (Updating the <code title="">default*</code> IDL - attributes causes content attributes to be updated as well.)</p></dd> - - </dl> - - <p>User agents may add DOM changes to the <span>undo transaction - history</span> of the <span>editing host</span>'s - <code>Document</code> object each time an action is triggered.</p> - - </div> - - <h4>Editing APIs</h4> <p>The definition of the terms <dfn>active range</dfn>, <dfn>editing