Closed
Bug 583010
Opened 14 years ago
Closed 14 years ago
Some images refuse to load when page is reloaded
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: shane.bundy, Unassigned)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b3pre) Gecko/20100729 Minefield/4.0b3pre
Build Identifier: Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b3pre) Gecko/20100729 Minefield/4.0b3pre
When a Facebook page is reloaded, some images do not load.
Reproducible: Sometimes
Steps to Reproduce:
1. Go to a Facebook user's page
2. Reload the page
Actual Results:
Some images do not show.
Expected Results:
All images should show as normal.
Reloading the page again solves the problem, but not permanently.
Reporter | ||
Updated•14 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Comment 3•14 years ago
|
||
Shane, did this just start as of tonight's nightly?
Comment 4•14 years ago
|
||
Could be a dup of the regression from the redirect changes.
Comment 6•14 years ago
|
||
This did start as of tonight's nightly. Also, in case it wasn't obvious, it affects nearly every page, not just facebook.
What bug is the redirect changes and what bug is the regression?
OS: Windows XP → All
Hardware: x86 → All
Comment 7•14 years ago
|
||
Bug 513086. There was no separate bug for the regression, just a followup fix pushed earlier today.
Comment 8•14 years ago
|
||
I'm seeing this on images that are not redirected at all, so I think bug 572520 (make all imgIDecoderObserver notifications asynchronous) is a more likely candidate.
Keywords: regression
Comment 9•14 years ago
|
||
Though "redirected" need not be just HTTP redirects... it can include stuff with proxies, etc, etc. We'll know once someone tests a build with the redirect fix, I guess.
Comment 10•14 years ago
|
||
(In reply to comment #8)
> I'm seeing this on images that are not redirected at all, so I think bug 572520
> (make all imgIDecoderObserver notifications asynchronous) is a more likely
> candidate.
It is not, this is clearly what is described in bug 513086 comment 79 and fixed by patch in comment 87.
(We had to open a new bug for that regression, this bug could then be easily closed as dup of that)
Comment 11•14 years ago
|
||
So, are people still seeing this bug since the redirect fix landed? Honza's comment 10 implies that it should be fixed now.
Comment 12•14 years ago
|
||
This is indeed fixed for me now.
Comment 13•14 years ago
|
||
Fixed by attachment 461244 [details] [diff] [review].
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Resolution: FIXED → WORKSFORME
Updated•14 years ago
|
blocking2.0: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•