Hi @igrigorik, hi @jaffathecake, we encountered a big problem with HTTP/2 priorities and Service Workers: https://medium.baqend.com/chromes-service-workers-break-http-2-priorities-649c4e0fa930 … Since the option to pass priorities for fetch() are nothing for the near future, are there plans to improve Service Worker prio logic in Chrome?
I actually don't care about the mapping. Browsers are going to do what browsers are going to do on both sides of the fetch() API. This seems obvious?
-
-
Anyway, what's important is that within whatever limited window of expression browsers actually give a tab/SW/API, we need to be able to express the same range of options.
-
And the incoming priorities might not match across browsers...so what? And outgoing fetches might get rescheduled or bumped in some way because browser knows best...also, so what?
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.