Closed Bug 1919158 Opened 2 months ago Closed 2 months ago

Request urgency may ignore fetchPriority and supportsPriority in two scenarios

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox132 --- fixed

People

(Reporter: acreskey, Assigned: valentin)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

We call nsHttpHandler::UrgencyFromCoSFlags(uint32_t cos, int32_t aSupportsPriority) to calculate the urgency for a request, using class of service and provided nsiSupportsPriority (which also reflects fetchPriority).

However in two scenarios we don't pass in the aSupportsPriority field, and so only calculate urgency from class of service:

Http2StreamBase::UpdatePriority

HTTP3Stream constructor

These may affect the urgency on PRIORITY_UPDATE frames?

Severity: S2 → S3
Whiteboard: [necko-triaged]
Assignee: nobody → valentin.gosu

This looks to be related to deprioritizing tabs as they are backgrounded/foregrounded.

Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/a2a4a88ef8d1 Pass nsISupportsPriority to UrgencyFromCoSFlags r=acreskey,necko-reviewers,kershaw
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/82766c877c09 Pass nsISupportsPriority to UrgencyFromCoSFlags r=acreskey,necko-reviewers,kershaw
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: