Closed Bug 1865394 Opened 11 months ago Closed 6 months ago

Verify dev tools display of priorities; urgency / incremental

Categories

(Core :: Networking: HTTP, task, P3)

task

Tracking

()

RESOLVED FIXED
126 Branch
Tracking Status
firefox126 --- fixed

People

(Reporter: acreskey, Assigned: dotoole)

References

(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.

We can move this to dev tools, but I'd like to take a look first and verify.

Whiteboard: [necko-triaged]
Severity: -- → S3
Priority: -- → P3

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.

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.

Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-next]

Depending on what we want to do exactly, this could be a dupe, noting as see also for now.

See Also: → 1758525
Assignee: nobody → dotoole
Whiteboard: [necko-triaged][necko-priority-next] → [necko-triaged][necko-priority-queue]

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?

Flags: needinfo?(valentin.gosu)

(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.

Flags: needinfo?(valentin.gosu)

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&regexp=false

Attachment #9379277 - Attachment description: WIP: Bug 1865394 - added urgency and incremntal priority header to request header in netmonitor → Bug 1865394 - added urgency and incremental to request header in netmonitor. r=valentin
Pushed by dotoole@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d1d9d57a9895 added urgency and incremental to request header in netmonitor. r=necko-reviewers,extension-reviewers,devtools-reviewers,valentin,robwu,bomsy
Pushed by dotoole@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/73f0a43c3ec3 added urgency and incremental to request header in netmonitor. r=necko-reviewers,extension-reviewers,devtools-reviewers,valentin,robwu,bomsy,webdriver-reviewers,whimboo
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
Status: RESOLVED → REOPENED
Flags: needinfo?(dotoole)
Resolution: FIXED → ---

Still more work to do

Status: REOPENED → RESOLVED
Closed: 7 months ago6 months ago
Resolution: --- → FIXED
Duplicate of this bug: 1758525
See Also: 1758525
See Also: → 1894758
Component: Networking → Networking: HTTP
No longer depends on: 1882782
See Also: → 1864392
Blocks: 1894758
See Also: 1894758
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: