[whatwg] Ongoing work on an editing commands (execCommand()) specification

[Ryosuke Niwa]

Great to see some spec'ing work here.  Some issues with your document:

   - Styling a Range doesn't support styleWithCSS=false
   - Ignores possibility of JavaScript modifying DOM while your algorithm is
   running - This is actually consistent with TOT WebKit where dispatches of
   DOM mutation events are delayed until the editing command finishes its
   algorithm.
   - Unstyling a Range doesn't work for text decorations because overriding
   text-decoration property doesn't clear underline nor line-through.
   - Styling a Range / Unstyling a Range doesn't seem to split the range
   into segments of phrasing contents.  How does your algorithm avoid wrapping
   a non-phrasing element with a span? (e.g. we don't want to wrap div,
   blockquote, etc... with a span)

- Ryosuke

On Wed, Mar 2, 2011 at 3:36 AM, Aryeh Gregor <Simetrical+w3c at gmail.com>wrote:

> Two or three weeks ago I began writing a specification for
> execCommand() and related functions.  I don't have anything
> implementable yet -- it's very incomplete and there are known issues
> with the existing stuff.  But I thought I'd post it for any early
> review comments on the direction I'm taking, particularly from
> implementers but also from anyone else familiar with the APIs (e.g.,
> someone who's used them in practice):
>
>
> http://aryeh.name/gitweb.cgi?p=editcommands;a=blob_plain;f=editcommands.html;hb=HEAD
>
> The plan is that this should be merged into the main HTML spec, with a
> full test suite, by the end of August.  Feedback appreciated.
>