Closed Bug 588282 Opened 14 years ago Closed 14 years ago

Random favicons in sidebar are not displayed until a mouseover

Categories

(Core :: Graphics: ImageLib, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: fehe, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b4pre) Gecko/20100817 Minefield/4.0b4pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b4pre) Gecko/20100817 Minefield/4.0b4pre ID:20100817131637 When decode-on-draw is enabled, random favicons in the sidebar do not display until they receive a mouseover. This happens only when decode-on-draw is enabled. It is not a discarding issue, as the bug does not happen if discarding is enabled but decode-on-draw is disabled. You see this with history sidebar, when in "By Last Visited" mode. Reproducible: Always Steps to Reproduce: 1. Configure History sidebar to view "By Last Visited" 2. Make sure you have a reasonable amount of browsing history (at least enough to fill the length of the history sidebar) 3. Enable image.mem.decodeondraw, but make sure image.mem.discardable is disabled 4. Restart the browser 5. Open History sidebar 6. Notice that some favicons do not display until you mouseover 7. Compare this with image.mem.decodeondraw disabled.
Version: unspecified → Trunk
Blocks: 573583
Summary: Random favicons in sidebar are not displayed unit a mouseover → Random favicons in sidebar are not displayed until a mouseover
I suspect bug 589815 may have fixed this. Will confirm later.
Too many check-ins within relevant window, so can't confirm which one fixed it, though I still suspect bug 589815. Resolving WFM. Mozilla/5.0 (Windows NT 5.1; rv:2.0b5pre) Gecko/20100824 Minefield/4.0b5pre ID:20100824040950 http://hg.mozilla.org/mozilla-central/rev/9a623cc1c5e7
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
(In reply to comment #2) > Too many check-ins within relevant window, so can't confirm which one fixed it, > though I still suspect bug 589815. It was almost certainly that bug - I landed it specifically to fix the favicon issues.
You need to log in before you can comment on or make changes to this bug.