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

@Jamesernator that's a good analogy but you'll find few (if at all) places in the DOM that have this behaviour. Event listeners for example "wrap" error handling internally and call the host error handler rather than "throw it back" to the `dispatchEvent` call.

@domenic I think I was confused about how this works?

If a user does 

```js
const ac = new AbortController();
const fetchResult = fetch('.../', { signal: ac.signal });
ac.abort(new TypeError());
```

Is `fetchResult` rejected with an `ERR_ABORT` DOMException and the user can access `ac.signal.reason` for metadata or is the goal (eventually) for promise APIs to reject with `ac.signal.reason`?

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