Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211) from Anne van Kesteren on 2022-10-10 (public-webapps-github@w3.org from October 2022)

From: Anne van Kesteren <notifications@github.com>
Date: Mon, 10 Oct 2022 07:23:06 -0700
To: whatwg/webidl <webidl@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/webidl/pull/1211/c1273394838@github.com>

I see, I think there used to be a requirement that optional cannot be followed by non-optional, but I cannot find that now.

> I also find it a bit confusing that a spec that defines a new interface inheriting from DOMException will also define a new, matching, error name, but that error name won't be present in that table. Or will it?

I think it would make sense to add these (as well as a reference to the class) to encourage reuse.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/pull/1211#issuecomment-1273394838
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1211/c1273394838@github.com>

Received on Monday, 10 October 2022 14:23:18 UTC