[Webkit-unassigned] [Bug 83993] Unsupported commands in execCommand/queryCommand* should throw except queryCommandSupported

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=83993





--- Comment #18 from Ehsan Akhgari [:ehsan] <ehsan at mozilla.com>  2012-04-17 08:22:55 PST ---
(In reply to comment #17)
> IE has always thrown, but other browsers (except Opera) have always not.  What this means is that there are probably pages that use IE-specific commands, and therefore would throw in Gecko/WebKit if they changed to match IE, although they don't currently throw in any browser.  So on second thought, there is a real compat risk here.  IE supports all sorts of crazy commands that no one else will want to.
> 
> I like the idea of throwing, but it might be too late.  Instead, browsers can return false from execCommand if it's not supported.  This is what current Gecko/WebKit do.  Likewise for queryCommandEnabled.
> 
> But for queryCommandIndeterm/State/Value, we can still throw -- this is what both IE *and* Gecko have always done, so for web content it's only a compat risk for WebKit if there's some command that IE *and* Gecko support but WebKit doesn't.  For WebKit-specific content, why would anyone be running a command that WebKit doesn't support?
> 
> How does this sound to everyone?

If WebKit is not willing to change the behavior, I'd be fine with this.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.