Are you talking about the horse story or in general?
It is actually quite simple
- Disabling the URL change on scroll makes scrolling smoother. I can personally see it and experince it after all I open this topic as bug. I was even able to record fps graph to shows the drops, drops that are translated on my computer to scrolling lag.
The fact that I was able to eliminate the lag by disabling the feature using js, is more then enough for me to understand the correlation.
the CPU example was to explain that I can “overclock” my machine to be faster, use more battery so I can have smooth scroll, but I don’t really have to because I can have smooth scrolling by tweaking the js, which is enough proof, that this feature could be improved on the code level(without losing the functionality). And that a fix is not necessarily hardware dependent.
I was able to replicate the issue in 4 different ways of input ( all on the same machine )
- scrolling using the laptop trackpad (1st used when I noticed the issue)
- using a mouse but dragging the scrollbar handle
- dragging the screen up and down using the touchscreen
- using the keyboard down/up arrow
(I have used the keyboard key down to run the tests and the fps recording.)
but if you are using the mouse scroll by rotating or swiping it (middle button) then this scroll is more likely incremental scroll which is obviously more difficult to see lag using it even on “low end machines”
Another symptom is when I experience the lag in the scroll the favico on that chrome/tab may flicker.
I opened this topic to raise awareness of a problem I personally experience.
I contributed my finding hoping that it can benefit the community and the project.
@sam helped me to isolate the culprit and testing performed returned with positive results.
fixing this issue may not affect everyone, but it is evident enough that there is a problem.
I am actually curious to know if more people experience that issue , but so far you and @cawas are the only people so to contribute their personal experience with the issue. I think that further investigation should be taken place.
I wish there was an easy way to prove that the issue is just there unfortunately it is a tricky one.
I originally suggested setting up a test topic and ask for users feedback to the scrolling experience.
sort of like A/B testing.
but may be this issue is really that minor that is not worth the effort.