Closed Bug 738881 Opened 14 years ago Closed 14 years ago

JPEGs won't load in background tabs

Categories

(Firefox :: Untriaged, defect)

11 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: j_marcovitch, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0 Build ID: 20120312181643 Steps to reproduce: Trying to open an image in a thumbnail gallery in a background tab.Using either the extension Easy Drag To GO to drag a thumbnail image to a new background tab or used Firefox itself open image's in a background tab command. Actual results: When I get around to clicking on those closed tabs the image would not be there. It would not just be there ready to view as in previous Firefox versions. Opening complex websites in background tabs is not affected. When I click the background tab, the entire linked website is there perfectly. Expected results: Even if I saved 20 images from a thumbnail gallery, when I clicked on that background tab image should be there ready to view.
WFM Does the issue still occur if you start Firefox in Safe Mode? http://support.mozilla.com/en-US/kb/Safe+Mode How about with a new, empty profile? http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile
Please provide an example link of such a page. I remember a checkin about optimizations for background tabs to reduce memory.
In addition to providing an example and testing in a new profile, as requested above, please let us know what actually happens when you switch to such a tab? Does the image not display at all? Does it take a short time to display (< 1 second) or does it appear to load over the network (which is usually slower)? Matthias is right, the images in background tabs are stored in compressed format and are only decompressed as you switch tabs.
Whiteboard: [closeme 2012-05-10]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2012-05-10]
You need to log in before you can comment on or make changes to this bug.