Closed Bug 1466992 Opened 3 years ago Closed 6 months ago
Menu items are poorly rendered when scrolling
1. Visit the site https://material.io/design/ 2. Tap on the menu button 3. Scroll down the menu panel When scrolled, the menu items behave badly as shown in the screenshot below. This issue does not occur in Chrome 66, Android 7.0. However, this issue may spread out to more websites using Material Design Components for Web. https://webcompat.com/uploads/2018/5/326dd1d6-08ed-4a26-b789-0fe0f1c98497.jpg
tracking-fennec: --- → ?
Hardware: Unspecified → All
This seems like grahic layers APZ issue not a perf issue.
Whiteboard: [webcompat] [qf] → [webcompat] [qf-]
(In reply to Karl Dubost :karlcow from comment #0) > When scrolled, the menu items behave badly as shown in the screenshot below. Specifically, the menu-items jitter / blink **while being scrolled**. This feels APZ-ish -- kats/botond, would you mind taking a look at this from an APZ perspective?
It looks like this page is just continually repainting even when it appears idle. And the compositor side layer tree is constantly changing with respect to the number and arrangement of layers. I don't understand what's going on. It does seem like an APZ issue, but it's going to be painful to debug.
Actually it might be that there's so much spew to logcat that it's dropping output, making it look like the layer tree is changing. And the infinite painting happens on desktop as well, causing my laptop to get quite hot.
Filed bug 1469947 for the perf implications, which we can keep separate from the visual glitching on Android. However, the visual glitching will be a lot easier to investigate if the painting isn't going full-throttle.
Depends on: 1469947
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5
Webcompat Priority: --- → ?
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.