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

> You can still skip it if the fetch doesn't have an Observer attached at all.

Sure, but if someone is listening for priority changes (rare), we would still have to queue runnables for every state change (multiple per fetch).

> The other way to do it would have it be like performance and/or MutationObserver, where the value is always read directly from the live state (a la performance.now() or MutationObserver's takeRecords()), and when the change callback / event fires, it aggregates all changes that happened between the last instance of the callback and now (a la MutationObserver's observe()).

Those APIs do not have to deal with cross-thread data AFAIK.

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