Support fetchpriority in Early Hints preloader
Categories
(Core :: Networking: HTTP, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: manuel, Assigned: fredw)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged], [wptsync upstream])
Attachments
(1 file)
This will probably only show minor improvements if improvements at all, but we might still want to implement it. See D197493#6954643
Updated•8 months ago
|
Assignee | ||
Comment 1•5 months ago
|
||
Assignee | ||
Comment 2•5 months ago
|
||
I haven't had time to investigate much on this, but just uploaded a patch to remember that there is some WPT tests we could probably rely on https://github.com/web-platform-tests/wpt/issues/8374#issuecomment-2085325404
Updated•4 months ago
|
Assignee | ||
Comment 3•4 months ago
|
||
I attached a patch with tests. Good news is that when the headers of early hints is parsed the fetchpriority attribute is already taken into account for adjusting the internal priority of the request (this is what the tests verify). I haven't checked yet if something like D209236 would then be enough to take that internal priority into account for early hints too.
Updated•4 months ago
|
Assignee | ||
Comment 4•4 months ago
|
||
(In reply to Frédéric Wang (:fredw) from comment #3)
I haven't checked yet if something like D209236 would then be enough to take that internal priority into account for early hints too.
Talking to valentin, such tests are probably not necessary so I'll land the patch as is.
Comment 7•4 months ago
|
||
bugherder |
Description
•