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

> If someone gets a handle on your signal object they can also make the aborted property lie, right?

That part is secured by the spec. `aborted` is a readonly property

I we really want the Controller/Signal distinction to make sense, what could potentially be done, while `AbortSignal` extends `EventEmitter`, is to tell that its `dispatchEvent()` would fail (throw?) when called, at least if the event type is `abort`

Regarding polyfills, it's still easy with Symbols to let the AbortSignal expose access to the `super.dispatchEvent()` more privately to the `AbortController`

Out of that topic, the `EventEmitter` dependency prevents this API from following the same path than Promises to the ECMA spec and then to core JS engines shared with servers, react-native, ... ;-(

-- 
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#issuecomment-530801593