Why are we using LOAD_BACKGROUND for lazy-loaded images?
Categories
(Core :: Layout, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(1 file)
It seems to me they shouldn't be LOAD_BACKGROUND. Once they get loaded they should be high priority, right?
Assignee | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
I don't have answers on this. Honza told me in a review comment, we can't change it once after we added the request into load group. https://phabricator.services.mozilla.com/D61437#inline-375510
I suppose you mean once the request gets started, no?
Assignee | ||
Comment 2•5 years ago
|
||
No, I mean that the request for these images should be high priority. We know they're about to be displayed to the user.
Comment 3•5 years ago
|
||
Ok, so you are suggesting a new load flag which doesn't block window.onload but is higher priority than LOAD_BACKGROUND, right? That makes sense to me.
Assignee | ||
Comment 4•5 years ago
|
||
Ah, d'oh, so I was wrong. I somehow thought that LOAD_BACKGROUND
was about priority, not just about bypassing the loadgroup...
Assignee | ||
Comment 5•5 years ago
|
||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)
Ah, d'oh, so I was wrong. I somehow thought that
LOAD_BACKGROUND
was about priority, not just about bypassing the loadgroup...
Yes, only difference is that such marked requests don't block onload and as such don't spin the throbber. I believe the LOAD_BACKGROUND flag is in place here.
Comment 8•5 years ago
|
||
bugherder |
Description
•