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?
-
-
FWIW, in one of the last webperfwg meetings,
@toddreifsteck showed interest in explicitly defining priorities and their mapping (rather than, or on top of, "upgrade"/"downgrade" hints). So there may be multi-vendor interest in explicit definition(which we can then map to H2 prio) -
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?
- 5 more replies
New conversation -
-
-
Some version of settable priorities is much more satisfying because there will be cases where naively copying the previous priority will be a bad idea. Or where you won't want to pass the original `Request` unmodified.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.