24000 2013-12-05 08:33:20 +0000 DOMException should extend ES Error 2013-12-09 14:26:45 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Windows 3.1 RESOLVED DUPLICATE 23367 P2 normal --- 1 w3c annevk mike Ms2ger w3c www-dom public-webapps-bugzilla oldest_to_newest 97167 0 w3c 2013-12-05 08:33:20 +0000 To make DOMException Promises friendly, the DOMException IDL definition needs to extend ES Error. See: https://github.com/domenic/promises-unwrapping/issues/84 Testing the following: <script> try { document.body.appendChild(document.body) } catch (e) { alert(e instanceof Error) } </script> The latest versions of Chrome, Safari, and IE return true. FF returns false. 97289 1 Ms2ger 2013-12-08 08:31:57 +0000 I think http://heycam.github.io/webidl/#es-exceptions already requires that. 97293 2 w3c 2013-12-08 13:36:58 +0000 (In reply to Ms2ger from comment #1) > I think http://heycam.github.io/webidl/#es-exceptions already requires that. Why not just make it explicit? It seems we missed this in Gecko ... could it be possible that happened because DOMException does not specify it explicitly? 97294 3 Ms2ger 2013-12-08 14:19:10 +0000 No, that happened because there was no real spec for this when we implemented DOMException as an interface in 2001. 97298 4 w3c 2013-12-09 00:15:45 +0000 I'm still not happy that the DOM Spec does not clarify this (or just make it explicit). It should at least contain a note. 97321 5 annevk 2013-12-09 14:26:45 +0000 It is explicit by not using "interface" but "exception". However, it sounds like what you want is a duplicate of a bug I filed a while ago. *** This bug has been marked as a duplicate of bug 23367 ***