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

@annevk isn't that a big breaking API change potentially changing how code passing an external signal to `fetch` should behave?

I am wondering if I am missing something since it feels like the API surface of AbortSignal `exploded` and (more importantly) the responsibility of "what do I throw with" moved from each API to the signal?

Would Node.js still be at liberty to _not_ reject with `signal.reason` in order to provide stronger guarantees to users regarding what core methods throw? 

-- 
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-977758998