Closed
Bug 1900764
Opened 6 months ago
Closed 5 months ago
urgency of fonts in fetchpriority-urgency.h2.html are not affected by fetchpriority
Categories
(Core :: Networking, defect, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
129 Branch
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: fredw, Assigned: fredw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Currently network.fetchpriority.adjustments.link-preload-font.low=20 and I expect the result to be similar to kExpectedRequestsOfLinkPreloadFont . But in fetchpriority-urgency.h2.html, the urgency is always 2.
|
||
Comment 1•6 months ago
|
||
Hey :fredw, will you working on a fix for these?
Severity: -- → S3
Flags: needinfo?(fwang)
Priority: -- → P2
Whiteboard: [necko-triaged]
|
Assignee | |
Comment 2•5 months ago
|
||
I plan to take a look at what's happening after bug 1881040 is closed (which adds a similar test).
Assignee: nobody → fwang
Flags: needinfo?(fwang)
|
|
Assignee | |
Comment 3•5 months ago
|
||
Urgency was not affected by fetchpriority because the test uses wrong
name for the corresponding IDL attribute.
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/fc406f106599
Fix font test for fetchpriority-urgency.h2.html. r=valentin,necko-reviewers
|
||
Comment 5•5 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 months ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•