Re: [whatwg/webidl] Normative: Add DOMException cause (PR #1179)

This PR looks good to me as is. I don’t see it as important for JS developers to be able to distinguish between undefined and missing cause—how frequently do you want to check whether there is a cause at all?

I think it would be good if this PR could land so that web error classes have the significant benefit of this cause feature. This utility is much greater than the edge case being discussed above.

For some context for people coming from TC39: it is extremely useful for web specs to stick to WebIDL conventions. Previous attempts to deviate from this pattern (eg streams) were found to be highly complex without developer benefit and were later reverted.

I just don’t see why JS developers should care about this case, so I don’t see why it makes sense to invoke priority of constituencies. This is neutral for JS developers, and helpful for implementers. (It is also helpful for spec writers, but they are lower down on the totem pole.)

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

Message ID: <whatwg/webidl/pull/1179/c1614400421@github.com>