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?
-
-
Thanks for linking our paper in the bug. We indeed noticed this, but assumed this was known/because service workers weren't finished yet.
@slightlylate's rant on this is exactly what we found as well. Interested in the solution :)2 replies 0 retweets 2 likes -
Replying to @programmingart @EWErikWitt and
Two changes should happen (in decreasing order of likeliness): 1.) untouched `Request` objects should plumb their original priorities through when constructor-copied (maybe) 2.) real priority information should be exposed (and be settable) on `Request`
1 reply 0 retweets 1 like -
Replying to @slightlylate @programmingart and
@yoavweiss has been working on variants of the second for the past year or so. See:https://github.com/WICG/priority-hints/blob/master/EXPLAINER.md …2 replies 1 retweet 1 like
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.
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.