Re: [whatwg/streams] WritableStreamDefaultController.abortReason (#1165)

Apologies for coming in late with this question, but...

Can anyone elaborate on the specific behavior of needing to force `reason` to be a DOMException is `abort()` or `abort(undefined)` are called?

IOW, why shouldn't a developer be able to express the intent that there was no reason for an abort, and then elsewhere be able to detect that intent via an `undefined` value rather than needing to inspect the name/toString of an exception object.

Moreover, there's a bit of a confusing semantic signal, with the object being an *exception*... It kind of indicates that `reason` is *required*, and that calling `abort()` without an argument (or with an explicitly passed `undefined`) is wrong or bad. It never was *required* before `reason` was added, and even MDN treats/documents it as *optional*.

I would just like to understand this specific change. It had some significant negative impacts on my library.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1165#issuecomment-1044823414
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/streams/issues/1165/1044823414@github.com>