Scrolling goes too fast on some websites
Opened this issue · 0 comments
Couldn't find an issue for this bug so here it is.
Description
On some websites, doing a short scroll with enough speed makes it so the thumb will end at a different location on the webpage than where it started.
A video being worth a thousand words, here are some examples I caught on camera. Apologies for the ugly setup, I couldn't screenrecord properly and I don't have a stand so I made one with some boxes around. Note that my moves were quite "aggressive" to better showcase the bug but it also happens with softer moves.
There are two cases depending on the website:
- The bug can be reproduced every time
- It doesn't or rarely occurs
Case 1 example 1: fnac.com
My thumb started on the "Oneplus 9 Pro" image every time but it always landed off at the end of the scroll.
Case 1 example 2: myanimelist.net
Same thing here, I started the scrolls on the "Manga store" title. It is quite extreme here.
Also happens with lateral scrolling for some reason. My thumb always landed on the image next to the one it started the scroll on.
Case 2 example 1: amazon.com
The bug usually doesn't occur but it can on rare occasions. It took me multiple tries but I managed to catch some occurrences. In this video, it happened on the 2nd, 3rd, 4th and 5th scrolls (I always started the scroll on the "Stuffed Animals" title), after that it didn't occur anymore.
Case 2 example 2: ebay.com
Same thing here, occurred on the 2nd and 3rd scrolls. I always started on the "$25.67" price tag.
I always make short scrolls like that on day-to-day browsing and to be honest it is quite annoying. I never know where I will land when scrolling.
Version info and additional remarks
Bug confirmed on Yuzu 6.0.2 (Xiaomi Mi 10 Pro, MIUI 11, Android 10) and 5.0.2 (Sony Xperia XZ, Android 7.1.1).
It doesn't happen on other browsers. Example with the latest version of Habit Browser:
I noticed that the websites that fall in case 1 always have a fixed top header. Maybe it has something to do with it? Although if it does, I don't know why the bug would occur on lateral scrolling like in example 1.2.