Re: [webidl] DOMException function definition makes no sense (#55)

Right, agreed the spec as-is is inconsistent.

The question then is whether we'd want to:

1. Change the parts of the spec that treat DOMException as a platform object, in favor of treating it like the spec treats other Error types; or
2. Just treat it as an `interface`, probably similar to @travisleithead's but with a [Constructor], and then let all that fall out automatically.

(2) is certainly easier and has the advantage of matching ~3 browsers. Whereas (1) gives platform consistency. It seems like implementers are going to favor (2) so it might be best to just admit defeat on consistency here, but I'd like to think about this a bit more before saying that for sure.

---
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/55#issuecomment-119691205