Closed
Bug 612599
Opened 14 years ago
Closed 14 years ago
Gray lines when using content.scrollTo
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
fennec | 2.0b4+ | --- |
People
(Reporter: stechz, Assigned: stechz)
References
Details
Attachments
(3 files)
(deleted),
image/png
|
Details | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
cjones
:
review+
|
Details | Diff | Splinter Review |
Occasionally (on desktop and on Android) gray lines will appear in content when content scrolls.
This is reproducible on Fennec with this page:
http://people.mozilla.org/~bstover/invalidate.html
(press S to step, or any other key to scroll automatically)
Fennec also needs a patch that listens to scroll events from content, which will be attached shortly.
Comment 1•14 years ago
|
||
Note these are not actually gray lines, but actually lines where content is 'faded' as if a layer containing the content was blended to a white background, but not completely covering those pixel rows.
Assignee | ||
Comment 2•14 years ago
|
||
Assignee | ||
Comment 3•14 years ago
|
||
Without the patch, there are no lines but I see:
###!!! ASSERTION: Messed up quadants (ThebesLayerBuffer.cpp line 164)
Also, I was wrong; Fennec already listens for scroll events. This patch just ensures that setDisplayPort isn't called when content scrolls.
The problem may be easier to figure out with cjone's test browser XUL.
Assignee | ||
Comment 4•14 years ago
|
||
Reproducible on test-ipcbrowser.xul, with resolution and scale at 0.7.
Updated•14 years ago
|
tracking-fennec: --- → ?
Updated•14 years ago
|
tracking-fennec: ? → 2.0b4+
Updated•14 years ago
|
Assignee: nobody → ben
Assignee | ||
Comment 5•14 years ago
|
||
Assignee | ||
Updated•14 years ago
|
Attachment #501856 -
Flags: review?(jones.chris.g)
Updated•14 years ago
|
Attachment #501856 -
Flags: review?(jones.chris.g) → review+
Assignee | ||
Comment 6•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•