Closed
Bug 223690
Opened 22 years ago
Closed 22 years ago
background-image's not loaded until scrolled into view
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
People
(Reporter: steven, Assigned: jdunn)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
When you look at www.eurogamer.net, you can see that in their 'features' column
they have a small thumbnail next to each item. It seems Firebird prioritizes
image loading for images in the visible area first (which is good), but
completely ignores loading invisible ones until you scroll them into view.
In this particular case, these images are included through an inline
background-image style.
Note: I'm not sure if Firebird does load the images, but waits with drawing
them, or if it actually doesn't load them until they are really needed.
Reproducible: Always
Steps to Reproduce:
1. Clear browser cache
2. Visit http://www.eurogamer.net and wait for the page to load
3. Scroll the page downwards and watch the 'features column' thumbnails appear a
moment after being scrolled into view.
Actual Results:
There is a significant delay between scrolling the page and watching the images
appear.
Expected Results:
The images should appear immediately.
I have experienced this behaviour on several sites, but eurogamer is the best
example I can find.
Comment 1•22 years ago
|
||
Not Firebird specific. Same behavior can be observed in Mozilla 1.5 milestone.
->Browser, trying Image/Layout
Assignee: blake → jdunn
Component: General → Image: Layout
Product: Firebird → Browser
Version: unspecified → Trunk
Comment 2•22 years ago
|
||
*** This bug has been marked as a duplicate of 57607 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
Updated•8 years ago
|
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•