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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 20 12:04:06 PDT 2012


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





--- Comment #26 from Ehsan Akhgari [:ehsan] <ehsan at mozilla.com>  2012-04-20 12:04:02 PST ---
(In reply to comment #25)
> I don't think that you explained how this is different from setProperty. The situation is pretty much the same - we have an extensible set of commands, and don't raise exceptions. Are you just saying that it's an outlier?
> 
> > How many recently-introduced new features can actually be used without risk of completely breaking other browsers?
> 
> That's how setProperty and execCommand are better :)

No, that's how they're "different".  The fact of the matter is that web APIs which silently accept invalid parameters and suddenly become no-op instead of throwing are very rare.  The majority of APIs just throw when passed invalid arguments.  So I don't think that giving an example of an API which does silently accept invalid arguments is a very strong case supporting that execCommand should also do the same.

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



More information about the webkit-unassigned mailing list