Scroll is laggy in Quantum, only when console is not open
I've been working on an issue at work, that requires some elements to be "sticky", so their position gets to be updated on the scroll event.
In quantum, there is a visible lag that occurs. The frustrating part is, the lag does not occur when the developer console is open or in the pre-quantum version of firefox (or any other browser).
Turning off smooth scrolling makes a small impact as the lag is reduced, however, does not fix the issue entirely, and also is not a viable option because instructing customers to change their browser settings is laughable.
This appears to be a bug, unless there is some setting i'm unaware of that can be manipulated via javascript?
All Replies (5)
The browser all of a sudden, gave me a warning message and gave this a name: Asynchronous panning.
Then went on to explain that mozilla doesn't support dynamic styling for scrollbased events anymore: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Scroll-linked_effects
davemaison द्वारा सम्पादित
Do you have hardware acceleration turned on?
tomatoshadow2 said
Do you have hardware acceleration turned on?
Yes, but that's irrelevant. In the doc file the console eventually spits out, the laggy scrolling is a direct result of how the browser handles scrolling now. Which to me was a poor decision, because quantum doesn't fully support the only viable alternative, being "position: sticky"
OP is the hardware acceleration that cause this.....
Xtffox said
OP is the hardware acceleration that cause this.....
I said that hardware acceleration is irrelevant earlier because you cannot instruct your users to do something special for browser "X" to get site "Y" to function properly. That's just the fastest way to lose customers.
Let's say you're just trying out quantum for the first time, and your favorite site utilizes the scroll event for styling. You will probably never use quantum again because the experience would have been so bad.
Otherwise developers have to develop with quantum specifically in mind, and that is the same exact issue that has made internet explorer terrible and unusable.
davemaison द्वारा सम्पादित