On Mon, Sep 19, 2011 at 12:37 PM, Ryosuke Niwa rn...@webkit.org wrote:
Not throwing makes sense to me (at least for now). What value should they
return though?
State/indeterm should return false, value should return . For
state/indeterm, this is what IE/WebKit/Opera do (Gecko throws). For
On Mon, Sep 19, 2011 at 10:45 AM, Aryeh Gregor a...@aryeh.name wrote:
State/indeterm should return false, value should return . For
state/indeterm, this is what IE/WebKit/Opera do (Gecko throws). For
value, it's what Gecko/Opera do; IE and WebKit return boolean false,
but that's the wrong
On Mon, Sep 19, 2011 at 1:50 PM, Ryosuke Niwa rn...@webkit.org wrote:
Sounds like a reasonable solution to me. For what's worth, I think WebKit
used to return false all the time so I don't think this will cause a huge
compat. issue for us.
I've changed the spec (warning, large diff):
I'm still using the whatwg list, because discussion on whether using
public-webapps is okay is (of course) still ongoing:
http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1402.html
What should the correct behavior be in the following cases?
* queryCommand*(insertimage). Neither
On 11-09-15 4:39 PM, Aryeh Gregor wrote:
I think the exception-throwing behavior is preferable in principle,
but for compat, I suspect the right behavior is to always return
boolean false for state and indeterm, and for value. This
basically matches everyone but Gecko for commands where none
