Browsers all throw when you do DOMException() (tested: IE9, Firefox 11a1, Chrome 17 dev, Opera 12.00). The exception interface object is not a function. Is this section deliberately different from how browsers behave, or is it an error?
This was a fairly recent change to WebIDL--you can't expect all browsers to immediately switch their implementations ;-)
I thought this was a deliberate decision to better align with ECMAScript for the long term.
(In reply to comment #1)
> This was a fairly recent change to WebIDL--you can't expect all browsers to
> immediately switch their implementations ;-)
> I thought this was a deliberate decision to better align with ECMAScript for
> the long term.
Yes, that's what I recall too.
I'm fine with that. Then this bug should be marked WONTFIX, and I'll write test cases per spec that all browsers fail. I'm just file any discrepancies I find as possible spec bugs, since if all browsers agree on behavior then usually that's what we want to spec. I suggest that notes be added to the spec when it's known that the behavior disagrees with all browsers, so that it's clear that those parts of the spec are deliberate proposed changes from the status quo. They can be removed once we have a major browser shipping with the change.
Yes, this should be WONTFIX. Adding a note to the spec about being deliberately different from all existing implementations here would make me want to do it for all features, and that's probably a bit of a time sink.
Okay with me.