If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

HTTP cache v2: Don't use LoadUnblocked flag as cache priority load indication

RESOLVED FIXED in mozilla29

Status

()

Core
Networking: Cache
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: mayhemer, Assigned: mayhemer)

Tracking

Other Branch
mozilla29
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
According how this flag is defined and used (mainly for XHR to not be blocked on head css/js loads) it is not a perf win to consider them as a cache priority loads.  Cache is not blocked by any priority loading, so only affect is that the XHR will load a bit later, while expected to not have any major impact on page load and user experience performance.
(Assignee)

Comment 1

4 years ago
Created attachment 8365259 [details] [diff] [review]
v1
Assignee: nobody → honzab.moz
Status: NEW → ASSIGNED
Attachment #8365259 - Flags: review?(michal.novotny)
+1
(Assignee)

Comment 3

4 years ago
Michal, this should land before we do the temporary m-c testing.  Can give the one line-review a priority please?
Attachment #8365259 - Flags: review?(michal.novotny) → review+
(Assignee)

Comment 4

4 years ago
https://hg.mozilla.org/mozilla-central/rev/0eb2ba65a702
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
(Assignee)

Updated

4 years ago
No longer blocks: 957243
You need to log in before you can comment on or make changes to this bug.