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

> You often do not have a reference to the signal.

I don't agree with this claim – especially the "often" part

 Do you have any concrete examples where you need to handle abort errors without access to the `signal`? Instrumentation could also access it, eg. `fetch(… { signal })` provides it as a parameter, which the instrumentation could extract. Also, I'm not sure it makes sense for instrumentation to determine the difference – it seems like something that should be handled at the app level.

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