So browsers are trying to keep the pipe full. Wasted time in the critical path is wasted time. There's no other word for it. Being slightly wrong about priority is much worse than not issuing a network request with the channel would otherwise be empty.
-
-
The infuriating part of this is the condescension from the H/2 and network stack community. The fear that web developers will "just make everything high priority; then what?" is both real, true, and useless.
Show this thread -
We'll always need to intervene as the user's agent, but so long as JS is part of the platform, developers could *already* do whatevs; it might just have been the long way 'round.
Show this thread -
So it's worth flagging this effect, worth being upset, and perhaps even worth calling out all the folks who work on Chrome that haven't fixed it. But the problem isn't the implementation. It's harder and worse than that. It's a fundamental lack of respect for web developers.
Show this thread -
Taking control of the network shouldn't mean always getting down-ranked in priority. This sort of magic needs to be in developer hands: https://cs.chromium.org/chromium/src/third_party/blink/renderer/platform/loader/fetch/resource_fetcher.cc?l=124 …
Show this thread
End of conversation
New conversation -
-
-
I do get that it is super hard for the browser to assign priorities in an ad-hoc fashion. But how is an integer-based priority better? I feel weights and dependencies are way more expressive. If only developer could specify them in fetch()...
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.
