Remember: HTML doesn't actually define a priority system, so this is all an exercise to the implementer and browsers do simulated annealing to come to roughly-good heuristics (historically, based on bogus benchmarks, but we're doing better now; thanks for asking).
AFAICT, this is basically the the only place we ever try to modify priority of existing requests: https://cs.chromium.org/chromium/src/content/browser/download/download_request_core.cc?type=cs&sq=package:chromium&g=0&l=275 …
-
-
That said, I'm unsure how often this get used: https://cs.chromium.org/chromium/src/services/network/resource_scheduler.cc?type=cs&sq=package:chromium&g=0&l=1115 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I agree that changing priorities of an existing stream is rare; H/2 priority (specified when opening a stream) is valuable
-
Sure, but Alex's point is that when the stream is opened, the browser doesn't know much about the eventual priority (is that image in the viewport? How many resources will be discovered by this script executing? etc.)
- 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.