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

I think the design was too specialized before this discussion, and it seems to be getting more specialized.

Personally, I'm unsure of the value of passing a reason to `.abort`. Generally, I think it would be great if `AbortSignal` were just `Signal`. And merely a remote way to flip a flag and fire and event. What code does after it sees the flag is up to that code. It would be more useful beyond just cancellation, etc.

Providing a new `AbortError` type that people can throw and check for should be sufficient for identifying cancellation. And they could also use it for their own cancellation mechanisms, which definitely already exist in the wild now.

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