Closed
Bug 1255607
Opened 9 years ago
Closed 9 years ago
Twitter feed frequently gets clipped at the top or bottom when mousewheel scrolling
Categories
(Core :: Panning and Zooming, defect)
Core
Panning and Zooming
Tracking
()
RESOLVED
DUPLICATE
of bug 1256677
Tracking | Status | |
---|---|---|
firefox48 | --- | wontfix |
People
(Reporter: RyanVM, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: gfx-noted)
Attachments
(2 files)
+++ This bug was initially created as a clone of Bug #1251894 +++
Only happens with the mouse wheel, so I assume it's APZ. Has the same regression range as bug 1251894 as well. The patch there doesn't fix it, unfortunately.
Comment 1•9 years ago
|
||
It looks like regular checkerboarding to me, but the fact that it didn't occur before bug 1251894 says otherwise.
Comment 2•9 years ago
|
||
Er, before bug 1231538.
Reporter | ||
Comment 3•9 years ago
|
||
Scrolling it was jankier before that, though.
Comment 4•9 years ago
|
||
Oh, now it makes sense! Scrolling that particular part of the page didn't use APZ due to bug 1238571, which bug 1231538 fixed. So what you're seeing now really is just regular checkerboarding. Not much we can do here other than improving displayport sizes / positioning and making painting faster.
Whiteboard: gfx-noted
Comment 5•9 years ago
|
||
Ryan, can you repro the problem, then go to about:checkerboard, find the checkerboard report corresponding to it, copy the raw log from the textarea at the bottom, and attach it to this bug? That will give us info about the displayport size and scroll velocity and such which should help us understand it a bit better. Thanks!
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 6•9 years ago
|
||
Flags: needinfo?(ryanvm)
Comment 7•9 years ago
|
||
Shows that the paint took 584.651ms to get through, which seems pretty long. But yes, this is regular checkerboarding and I don't think it qualifies as a release blocker. Reducing the size of the displayport would probably help bring that paint time down, that seems to be main problem. Now that the displayport size tuning experiment (bug 1251052) has been running a while I'll re-analyze the telemetry data from that and try to figure out how much we can afford to trim the displayport by.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•