4 ms·
I just retested in case they fixed it and no [1]. The easiest way to tell it's non-native scroll is that Android has this effect when you reach the top or botto
by redox99 4y ago
I just retested in case they fixed it and no [1]. The easiest way to tell it's non-native scroll is that Android has this effect when you reach the top or bottom that it "stretches" the content. You can try it everywhere (even inside Firefox settings menu) and it will work like that, except for the actual webpage in Firefox.
Another difference in the scroll is that it has much higher friction (deceleration) in Firefox than native Android.
[1] Firefox 103.2.0 on a Samsung S20 with latest updates.
- 29083011397778 4y agoLittle late, but for the record, your first issue reeks of a Samsung-specific bug. My Pixel 2 running LineageOS stretches the same in the [phone] settings app as it does in the [Firefox] settings page. Samsung has always had weird quirks in the way their skinned Android runs, and AFAICT, were the absolute worst for causing app developer headaches in the earlier Android days. I would be shocked if they've gotten dramatically better since.
- redox99 4y agoThe settings page stretches correctly. The issue is with the webpages.
- 29083011397778 4y agoI'm sure the settings page does - but because Samsung implements APIs a little differently, and this has caused devs issues in the past, I'm assuming the browser with a smaller dev team may have missed this quirk at first glance. Other Chrome-based browsers probably don't have this issue - Chrome's team is very well-funded, and forks likely benefit from Google doing the edge-case testing. Maybe Firefox is doing something weird, but I've got a coworker with that same phone - so at the very least I can compare my Pixel to his Samsung, and see who threw standards out the window.