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

That capability is useful in the same way that exceptions in general are useful.

A signal-accepting API is one which gives its caller some amount of control over what exceptions it throws/rejections it returns/etc. Those exceptions can communicate anything: sometimes an abort, sometimes a timeout, sometimes a TypeError, sometimes a HTTP error (in a Node server), etc. The caller could use its controller to control the function and have it give a TypeError in exactly the situations a TypeError would normally be appropriate. (E.g., the caller has done some further async validation work and realized that the inputs are bad.)

> Are there any non-third-state errors that are aborted with?

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