[whatwg] [editing] HTML Editing APIs specification ready for implementer feedback

Ehsan Akhgari ehsan at mozilla.com
Thu Aug 4 15:47:17 PDT 2011

Here's my feedback on sections 1-3.  I'll provide feedback on the rest 
of the specification in the near future.

* The "gecko" prefix should be changed to "moz", to be compatible with 
other Gecko specific prefixes.
* Do we have any other case where the HTML spec says that a browser can 
change its behavior if it's upgraded in the middle of the browsing session?

* Gecko currently has some problems in returning the correct status of a 
command based on the active range, so the results obtained from Firefox 
here should not be a determining factor (see 
* On the same note, I actually think that WebKit's behavior makes sense. 
  We need to make sure that _something_ happens when the command is 
executed after making sure that queryCommandEnabled returns true.  If 
the beginning of the active range falls into an editable section, that 
would happen (perhaps to part of the range).  Initially I thought that 
it would be better to return true if any range in the selection falls 
into the editable section, but that wouldn't make a lot of sense if the 
range spans across multiple contentEditable sections.


More information about the whatwg mailing list