Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

Has there been any F2F on having a `statechange` event versus having *separate events for each kind of state change*? I'd really prefer *both*, especially as I see myself more frequently wanting the form factor of the *latter* than the former (ie. listening for a `responding` event rather than listening to every `statechange` event and manually filtering within to see if the state was changed to `responding`, which has been one of the most annoying things about working with XHR's `readystatechange` event).

-- 
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/fetch/issues/447#issuecomment-292366308