Verify dev tools display of priorities; urgency / incremental
Categories
(Core :: Networking: HTTP, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: acreskey, Assigned: dotoole)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged][necko-priority-queue])
Attachments
(1 file)
In the excellent talk, Resource Loading at the Cutting Edge, Robin Marx shows Firefox dev tools displaying incorrect priorities relative to the request urgencies.
The bug is to verify if this is the case and fix.
Related, dev tools does not appear to show the urgency/incremental headers.
Reporter | ||
Comment 1•1 year ago
|
||
We can move this to dev tools, but I'd like to take a look first and verify.
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Comment 2•1 year ago
|
||
I believe we are using the PRIORITY_UPDATE frame for HTTP/3 rather than the request header
(although this may change in Bug 1865040)
But we should verify that the class of service flags for the channels are correctly reflected in devTools and also propagated to neqo.
Reporter | ||
Comment 3•1 year ago
|
||
Valentin and DevTools team shed some light on this on:
DevTools is displaying the priority from nsISupportsPriority
https://searchfox.org/mozilla-central/rev/1a63fee6c2a8ea6846f6f16b85edeb6d19fc9f23/devtools/shared/network-observer/NetworkUtils.sys.mjs#196
But Necko also has a notion of 'ClassOfService'
https://searchfox.org/mozilla-central/rev/1a63fee6c2a8ea6846f6f16b85edeb6d19fc9f23/netwerk/base/nsIClassOfService.idl#23
To resolve this, Necko will provide a singular API to DevTools that unifies these concepts.
Reporter | ||
Updated•1 year ago
|
Depending on what we want to do exactly, this could be a dupe, noting as see also for now.
Hey Valentin, based on how robin marx shows that the devtools priority is not aligned with the urgency (u), would a possible approach be to map the mPriorityUrgency value, set here , to a priority value highest,high...lowest, then expose that to nsISupportsPriority.idl?
Comment 6•1 year ago
|
||
(In reply to Andrew Creskey [:acreskey] from comment #0)
Related, dev tools does not appear to show the urgency/incremental headers.
That's because we don't appear to set them.
(In reply to Dylan from comment #5)
Hey Valentin, based on how robin marx shows that the devtools priority is not aligned with the urgency (u), would a possible approach be to map the mPriorityUrgency value, set here , to a priority value highest,high...lowest, then expose that to nsISupportsPriority.idl?
I also think a problem here is that we don't yet fully implement fetchpriority (bug 1797715) - so the priorities won't match what we expect.
Comment 7•1 year ago
|
||
would a possible approach be to map the mPriorityUrgency value, set here , to a priority value highest,high...lowest
We already set the priority to match the CoS sometimes here and other times it's completely separate from it
https://searchfox.org/mozilla-central/search?q=nsCOMPtr%3CnsISupportsPriority%3E&path=&case=false®exp=false
Updated•11 months ago
|
Comment 10•11 months ago
|
||
Backed out for causing failures at browser_net_har_copy_all_as_har.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/d5bc130229070c4e63e755762fcafc37d4ecfcf6
Failure log: https://treeherder.mozilla.org/logviewer?job_id=450647075&repo=autoland&lineNumber=4136
Comment 11•11 months ago
|
||
Comment 12•11 months ago
|
||
bugherder |
Assignee | ||
Comment 13•11 months ago
|
||
Still more work to do
Updated•11 months ago
|
Updated•10 months ago
|
Updated•8 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Description
•