19110 2012-09-28 11:33:04 +0000 DOM "throw" algorithm doesn't seem to use WebIDL "throw" algorithm correctly 2012-12-06 09:23:38 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All Windows 3.1 RESOLVED FIXED P2 normal --- 1 ayg annevk cam mike www-dom public-webapps-bugzilla oldest_to_newest 74785 0 ayg 2012-09-28 11:33:04 +0000 http://dom.spec.whatwg.org/#concept-throw says to create a new DOMException, "set" its name and message to something, and then "throw" it in the WebIDL sense. But WebIDL's throw algorithm http://dev.w3.org/2006/webapi/WebIDL/#es-throwing-exceptions takes the name and message as optional arguments, not an existing exception object. Nothing says what it means to "set" the name and message (own properties? inherited?). I think the DOM algorithm needs to be rewritten to match the WebIDL one, because currently the combination doesn't make sense to me. Maybe you want something like Throw a DOMException, with name equal to name and message equal to an implementation-defined value. But you need to set the code attribute somehow. 75682 1 annevk 2012-10-09 14:24:05 +0000 Any suggestions heycam? 79524 2 cam 2012-12-06 05:13:31 +0000 I extended http://dev.w3.org/2006/webapi/WebIDL/#dfn-throw to take the values to assign to the exception fields, and changed the algorithm in http://dev.w3.org/2006/webapi/WebIDL/#es-throwing-exceptions to set them so. You can then say: Throw a DOMException, with name equal to name, message equal to an implementation-defined value, and with code set to blah. 79531 3 annevk 2012-12-06 09:23:38 +0000 Thanks! https://github.com/whatwg/dom/commit/9d1febdfc8d10a186387e1081d5810f4de3cba2b