Closed
Bug 1145278
Opened 9 years ago
Closed 9 years ago
Visible image glitches when scrolling http://www.google.com/makani the first time
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1144899
People
(Reporter: dholbert, Unassigned)
References
()
Details
Attachments
(2 files)
STR: 1. Visit http://www.google.com/makani (Shift+Reload if you've visited it before) 2. Hit spacebar or downarrow, to scroll to the next section. (and the next, and the next.) ACTUAL RESULTS: As sections scroll in, there are visible glitches with the scrolled-in background image (possibly from lazy decoding?). EXPECTED RESULTS: No such glitches. NOTE: This only reproduces the first time I scroll through the page. If I reload (without shift), or if I scroll back to the top (w/ mouse-scrollwheel) and then scroll down again, I don't hit the bug.
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Version info: Nightly 39.0a1 (2015-03-19) Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0 (It's possible this is a layers bug or a layout/animation bug, too. But I'm guessing, imagelib given that it's fixed after a reload, if you've scrolled through all the content -- and you can only re-break it by shift-reloading [forcing you to redownload/redecode images].)
Reporter | ||
Comment 3•9 years ago
|
||
Looks like this was a new regression in yesterday's nightly, actually. Likely a regression from bug 1124084 (which enabled the downscale-during-decode pref). Possibly a dupe of bug 1144899.
Reporter | ||
Comment 4•9 years ago
|
||
Yup, I confirmed locally that (1) I can reproduce this in a debug build, and (2) bug 1144899's patch fixes it. --> Duping to bug 1144899.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 5•9 years ago
|
||
Here's another screencast where the bug may be more obvious. In this one, I scroll through the page twice. The first time reproduces the bug; the second time does not. (since at that point, everything's decoded)
You need to log in
before you can comment on or make changes to this bug.
Description
•