[whatwg/dom] AbortSignal consumers can potentialy emit abort event on it (#784)

As many developers coming to the AbortController/AbortSignal API, I got a bit concerned by its "complexity", meaning... "Not a big deal but... Couldn't the signal & controller classes be merged?"

The main raised reason was about separation of concerns, forbidding a consumer to be able to call `abort()` on the signal

> see: 
> - https://github.com/whatwg/dom/issues/438#issuecomment-315995331
> - https://github.com/web-platform-tests/wpt/pull/6484#issuecomment-315775251

But looking at the API specification, I don't see anything preventing the consumer from calling `signal.dispatchEvent(new Event('abort'));`

I don't see much control on that topic in polyfills neither

Am I missing something ?

-- 
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/784