Open Bug 1944827 Opened 18 days ago Updated 12 days ago

nsISupportsPriority.priority is set to PRIORITY_NORMAL for a deferred JS request, which seems to be having an higher priority

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

People

(Reporter: ochameau, Unassigned)

Details

(Whiteboard: [necko-triaged][necko-priority-next])

Attachments

(1 file)

Attached image netmonitor timings

Analysing a forced reload (Ctrl+F5) on https://www.internetonmars.org/h3prios/fosdem/ff_lcpbeforedefer.html with the netmonitor will highlight a possible issue with nsISupportsPriority.priority attribute.

This is about https://www.internetonmars.org/h3prios/fosdem/assets/script_large.js?defer=true request.
DevTools reads the priority from Necko over here and I verified, nsISupportsPriority.priority is set to PRIORITY_NORMAL==0 for that request. (At least at the point in time where devtools query this attribute).

But looking at the timing chart in the netmonitor... the priority is most likely not NORMAL as it is schedule before the other ones?

Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-new]
Priority: P2 → P3
Whiteboard: [necko-triaged][necko-priority-new] → [necko-triaged][necko-priority-next]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: