Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033)

> The design doesn't allow for that. At least, it's not clear to me how you'd do that for `controller.abort(1)` or equivalent.

Indeed. Without access to the `signal`, code that wants to detect abort errors will need to rely on fallible heuristics, as is already done in node (someone could have made an `AbortError` that is not used for abort signals). Node will have to rely on assumptions / conventions for it to work.

Also, is it really an issue? If someone does `controller.abort(1)`, they will most likely catch any errors themselves, and handle it however they want.

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