Re: [whatwg/webidl] Proposal: DOMException.ignoreAborts(promise) (#933)

> you generally don't want to ignore timeouts for a fetch

That's consistent with our experience. Timeout is a result.

We do actually have checks like this in other cases, including one spot where there are _three_ DEX types that are expected and not considered exceptional:

```
      let shouldIgnore =
        check.isAbortError(err) ||
        check.isNotAllowedError(err) ||
        check.isNotSupportedError(err);
```

But this example only makes sense in its very local context. The way AbortError models a _type of completion_ instead of an abrupt _result_ seems unique.

It's like `break` forced to wear a humiliating `throw` costume that makes every `catch`  bouncer stop it at the door for an ID check. Or something? This justifies privileged API vis a vis other DOMException types.

-- 
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/webidl/issues/933#issuecomment-976962558