Open
Bug 1260215
Opened 8 years ago
Updated 2 years ago
Scrolling on verily.com is stuttery/janky
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: ehsan.akhgari, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: perf, Whiteboard: [gfx-noted])
Safari seems to be able to do a much more smooth job at scrolling https://verily.com/ than we can.
Comment 1•8 years ago
|
||
Could you verify that the page is async-scrolling, for example by enabling paint flashing (nglayout.debug.paint_flashing) and verifying that the page isn't repainted on every scroll? If so, a profile would be helpful to understand the slowdown. For me, testing on Linux, the page is async-scrolling, and my perception of the scrolling smoothness is fine (but I don't have Safari nearby to compare it to).
Keywords: perf
Whiteboard: [gfx-noted]
Comment 2•8 years ago
|
||
With paintflashing I see the background of the page (and many other parts) continuously repainting all the time, even if I'm not scrolling. OS X aurora build from March 17.
status-firefox48:
--- → affected
Version: unspecified → 48 Branch
Comment 4•8 years ago
|
||
Actually I'll file a new bug for the infinite painting, and mark this dependent on that. There might be more going on here, best to keep the issues separate.
Keywords: power
Comment 5•8 years ago
|
||
The infinite painting, combined with slow texture upload, are what's causing the stuttery scrolling. Texture upload happens on the compositor thread and blocks composition.
Comment 6•8 years ago
|
||
Trying to make sure all jank buga have "jank" in the summary.
Summary: Scrolling on verily.com is stuttery → Scrolling on verily.com is stuttery/janky
Updated•8 years ago
|
status-firefox49:
--- → affected
status-firefox50:
--- → affected
Depends on: 1261166
OS: Unspecified → Mac OS X
Priority: -- → P3
Updated•8 years ago
|
Updated•7 years ago
|
status-firefox52:
--- → wontfix
status-firefox53:
--- → affected
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•