Using scrollbar-width:none on root element causes severe scrolling issues with WR picture caching
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox71 | --- | unaffected |
firefox72 | --- | unaffected |
firefox73 | --- | verified |
People
(Reporter: jastekken, Assigned: gw)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
- Ensure WR and WR-picture-caching are enabled
- Load any page that would overflow the viewport
- Enter devtools style-editor and apply :root{ scrollbar-width:none }
- Initiate scroll
Actual results:
Viewport does not scroll at all or at least not smoothly.
Expected results:
Viewport should scroll smoothly or instantly.
The issue arises whether smooth scrolling is enabled or not.
I think this problem has likely been triggered by bug 1599656 or perhaps by bug 1599965
Comment 1•6 years ago
|
||
I can confirm. I use a userContent.css file with the following line:
*{ scrollbar-width: none }
It hides all scrollbars. Since around Nightly turned 73, it causes severe lag when scrolling unless I disable hardware acceleration in settings.
It happens on two different machines:
- Win10 64 bit with Pentium Gold G5400 with integrated graphics.
- Win8 32 bit with Nvidia GT 240.
Comment 2•6 years ago
•
|
||
It would be useful to run mozregression on this and see which changeset caused this. I can repro this, it is pretty visible in github for example (I was using this PR).
![]() |
||
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
Thank you Alice! (I couldn't get to it since I didn't have good enough internet when I wrote comment 2).
Glenn, can you take a look? Seems we're incorrectly skipping frames.
Updated•6 years ago
|
Assignee | ||
Comment 5•6 years ago
|
||
Yup, will look into this today.
Assignee | ||
Comment 6•6 years ago
|
||
Comment 8•6 years ago
|
||
bugherder |
Updated•6 years ago
|
Updated•6 years ago
|
Comment 9•6 years ago
|
||
I've managed to reproduce this issue using Firefox 73.0a1 (2019-12-04) on Windows 10x64 by following the STR from comment 0.
This is verified fixed using Firefox 73.0b12 on the following OSes: windows 10x64 and windows 8.1x64.
Description
•