Slow scrolling on www.ti.com/document-viewer
Categories
(Core :: Graphics: Layers, defect, P3)
Tracking
()
People
(Reporter: witold.baryluk+mozilla, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Visit
http://www.ti.com/document-viewer/ADS131M04/datasheet/fast-startup-response-sbas8908695
I am using Firefox 75.0, on Linux amd64, MATE / X11, with amdgpu (Radeon Fury X), and Mesa 20.0.4, under Linux 5.2.17.
Actual results:
The document area should scroll smoothly.
Expected results:
The scrolling is very slow. Using "smooth scrolling" disabled or enabled doesn't make a difference.
Enabling webrender in "about:config", seems to help a lot.
No issues in Chromium 81.0.4044.92
Reporter | ||
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 3•5 years ago
|
||
Thanks for reporting!
3 questions:
-
Would it be possible to get a performance profile of both with and without webrender ideally in Firefox Nightly release?
https://profiler.firefox.com/ -
Could you attach the information in about:support?
-
When Webrender is enabled, how does it compare to Chromium?
Thanks!
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
Hi Kris, of course.
All clean new profiles, with no extensions, and only one tab open.
- Firefox 75.0 without webrender (default): https://perfht.ml/3aHASqk
- Firefox 75.0 with webrender enabled: https://perfht.ml/3bHKEKo
I would say Firefox 75.0 with Webrender enabled, looks to be as fast as Chromium. (the window redraw with new content after scrolling by one tick with my mouse whell, has so small lag, that I can't really say which one is faster just by looking at it).
- Firefox Nightly 77.0a1 (2020-04-23): I just tested it with default settings (no webrender), and it looks to be working quickly (even with no webrender enabled). https://perfht.ml/2S6jeWD
Reporter | ||
Comment 5•5 years ago
|
||
Reporter | ||
Comment 6•5 years ago
|
||
Comment 7•5 years ago
|
||
Thanks Witold, that's good news :)
I'm going to close the issue as future releases should solve this.
Let us know if this issue pops up again on future releases.
Kris
Description
•