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

We discussed this today on the WinterCG call. Most of the attendees did not have strong opinions one way or the other with regard to `cause` as an accessor or `cause` as a data property. However, those that did have strong opinions were in favor of matching the behavior specified by TC-39 for `Error` objects.

Specifically from the Cloudflare Workers point of view, because we are aligned with WebIDL, it is easier for us to implement `cause` as using an accessor, and in our typical use case we would treat a missing `cause` and a `cause` that is always `undefined` as being semantically equivalent, however there is a valid argument to make that a cause that is explicitly `undefined` vs. a `cause` that just was never provided are very different things and should be treated as such. Unless there's a strong technical argument to make in favor of the accessor option beyond "that's what we do for `name` and `message` so let's keep it consistent", I'd prefer that `cause` on `DOMException` was defined as an own data property.

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

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