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

Tim Down timdown at gmail.com
Wed Apr 6 16:40:02 PDT 2011

Is there an overwhelming reason why execCommand() should be restricted
to contentEditable/designMode elements, as the spec seems to suggest?


On 1 March 2011 18:36, 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.

More information about the whatwg mailing list