Closed
Bug 612599
Opened 15 years ago
Closed 15 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)
|
368.93 KB,
image/png
|
Details | |
|
1.13 KB,
patch
|
Details | Diff | Splinter Review | |
|
1.11 KB,
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•15 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•15 years ago
|
||
| Assignee | ||
Comment 3•15 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•15 years ago
|
||
Reproducible on test-ipcbrowser.xul, with resolution and scale at 0.7.
Updated•15 years ago
|
tracking-fennec: --- → ?
Updated•15 years ago
|
tracking-fennec: ? → 2.0b4+
Updated•15 years ago
|
Assignee: nobody → ben
| Assignee | ||
Comment 5•15 years ago
|
||
| Assignee | ||
Updated•15 years ago
|
Attachment #501856 -
Flags: review?(jones.chris.g)
Updated•15 years ago
|
Attachment #501856 -
Flags: review?(jones.chris.g) → review+
| Assignee | ||
Comment 6•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•