Closed
Bug 795694
Opened 13 years ago
Closed 13 years ago
Content not redrawn after reversing scrolling direction on "The Verge" homepage
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
mozilla18
| Tracking | Status | |
|---|---|---|
| firefox17 | --- | unaffected |
| firefox18 | + | verified |
People
(Reporter: timbugzilla, Assigned: mattwoodrow)
References
()
Details
(Keywords: regression)
Attachments
(3 files)
Since DLBI landed scrolling over top stories grid on The Verge's homepage then scrolling back to reveal them again shows regions where content has not been redrawn.
See attachments for a picture of the problem, and how the page should look.
This was observed with the moz-central win32 PGO build built from the following change-set:
http://hg.mozilla.org/mozilla-central/rev/a680fd777c3b
| Reporter | ||
Comment 1•13 years ago
|
||
Updated•13 years ago
|
Updated•13 years ago
|
tracking-firefox18:
--- → ?
I saw this yesterday and thought it was the same issue as bug 795695, but it's not.
I can still reproduce on linux-x64/basic and win7/d3d10.
| Assignee | ||
Comment 3•13 years ago
|
||
Attachment #666400 -
Flags: review?(roc)
Attachment #666400 -
Flags: review?(roc) → review+
| Assignee | ||
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Target Milestone: --- → mozilla18
Updated•13 years ago
|
Updated•13 years ago
|
Updated•13 years ago
|
Assignee: nobody → matt.woodrow
Comment 5•12 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20121205060959
Verified as fixed on the latest Nightly - the content is properly redrawn after reversing scrolling direction.
QA Contact: simona.marcu
Comment 6•12 years ago
|
||
(In reply to Simona B [QA] from comment #5)
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
> Build ID: 20121205060959
>
> Verified as fixed on the latest Nightly - the content is properly redrawn
> after reversing scrolling direction.
Correction - Verified as fixed on the latest Firefox 18 beta 3.
You need to log in
before you can comment on or make changes to this bug.
Description
•