- From: <bugzilla@jessica.w3.org>
- Date: Sun, 20 Nov 2011 17:01:19 +0000
- To: public-script-coord@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14877
Aryeh Gregor <ayg@aryeh.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Define [[Class]] of |Define [[Class]] of
|interface prototype objects |interface prototype
| |objects, exception
| |interface objects, and
| |exception interface
| |prototype objects
--- Comment #7 from Aryeh Gregor <ayg@aryeh.name> 2011-11-20 17:01:18 UTC ---
I just discovered that exception interface objects and exception interface
prototype objects also don't have [[Class]] defined. Browser behavior for
DOMException:
* IE9: DOMException and DOMExceptionPrototype, like regular interfaces
* Firefox 11a1: ???
* {}.toString.call(DOMException) == "[object DOMPrototype]"
* String(DOMException) == "[object DOMException]"
* {}.toString.call(DOMException.prototype) == "[object
XPC_WN_ModsAllowed_NoCall_Proto_JSClass]"
* Chrome 17 dev: Function for the exception interface object, Object for the
exception interface prototype object
* Opera 12.00: DOMException for both objects
(Of course, String(DOMException.prototype) throws in all browsers because it
invokes Error.prototype.toString.)
I'd go with IE9 here, unless it has compat issues.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Sunday, 20 November 2011 17:01:20 UTC