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

> the browser may be adjusting priority as the user scrolls the page - finding out about that in the service worker would have to be async, no?

Oh, CHANGES in priority have to be async, of course. Those are *events*.

The key point that I'm trying to make is that that doesn't mean the scripting thread needs a guarantee that it'll have *seen* the priority-change event before reading the changed priority. I mean, the network thread could *also* change priority *while we're handling the event for the last change*.

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