16454 2012-03-20 18:25:41 +0000 SomethingError 2012-03-21 23:00:50 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED FIXED http://dev.w3.org/2006/webapi/WebIDL/#ecmascript-throw P2 normal --- 1 w3c cam annevk mike public-script-coord public-webapps-bugzilla oldest_to_newest 65860 0 w3c 2012-03-20 18:25:41 +0000 The spec says "When an algorithm says to “throw a SomethingError” then this means to construct a new ECMAScript SomethingError object and to throw it, just as the algorithms in ECMA-262 do." But you only ever throw a TypeError (or I could not find any other type of error?). I think it would be better to have all throw TypeError just link directly to ECMAScript5. 65876 1 annevk 2012-03-20 20:16:21 +0000 Indexed DB does that. What is wrong with having a convenience hook? 65877 2 w3c 2012-03-20 20:26:18 +0000 (In reply to comment #1) > Indexed DB does that. What is wrong with having a convenience hook? Nothing wrong, if it does something. If in this case it doesn't do anything, then it is redundant. I would rather click on "throw an TypeError" and be taken straight to ECMAScript5 (rather than do a roundtrip). http://es5.github.com/#x15.11.6.5 65931 3 cam 2012-03-21 23:00:50 +0000 Yeah, sorry it would be good to have a link to the actual ECMAScript requirements. I've added a link from #dfn-throw to #es-throwing-exceptions.