Closed Bug 1348035 Opened 3 years ago Closed 3 years ago

Prioritize network loads according the active tab load phase

Categories

(Core :: Networking: HTTP, enhancement, P5)

enhancement

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox55 --- affected

People

(Reporter: mayhemer, Assigned: mayhemer)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [necko-active])

Goal: give large amount of bandwidth, overall, across origins, exclusively only to requests blocking a rendering phase the active loading tab is at.

The phases are yet to be determined exactly.  A phase example: before-first-paint, before-onload.

Question here is how to label the channel.  I'm afraid out priority strategies on channels are more "relative" than "absolute" to be safely and easily used.  Marking should be more explicit.  Probably adding aliases for current priority levels to make it more clear which priority to use for what would do.
Assignee: nobody → honzab.moz
Whiteboard: [necko-active]
Blocks: 1247843, 685740
Priority: -- → P5
So far we haven't found any other intermediate phase breakers that would be worth.  There are plans to move some loads after the page load or some time after the page load start.  That is sufficient for the overall CDP goal.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.