3 ms·

What do you mean by non-native scroll behavior? I'm asking seriously, never noticed anything.

by cycomanic 4y ago

idsout 4y ago
Also wondering. I've been using Firefox on Android for at least a couple years now. Works fine for me
- just_boost_it 4y ago
  Ditto for me.
qu4z-2 4y ago
I'm not the GP but I've noticed since the switch over to "New" Android Firefox (Fenix or whatever?) scroll events aren't handled properly. That is, dragging your finger around on the screen works, but any other source (keyboard, for example) does nothing. Maybe that's what they were referring to; maybe they have a different issue.
scq 4y ago
Firefox for Android used to implement scroll coasting in a way that felt very different from Chrome and native Android apps. I just gave it a try now and it seems like they've fixed it, scrolling feels native now.
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 ago
  Little 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 ago
    The settings page stretches correctly. The issue is with the webpages.
    - 29083011397778 4y ago
      I'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.

What do you mean by non-native scroll behavior? I'm asking seriously, never noticed anything.

idsout 4y ago

Also wondering. I've been using Firefox on Android for at least a couple years now. Works fine for me

just_boost_it 4y ago
Ditto for me.

qu4z-2 4y ago

I'm not the GP but I've noticed since the switch over to "New" Android Firefox (Fenix or whatever?) scroll events aren't handled properly. That is, dragging your finger around on the screen works, but any other source (keyboard, for example) does nothing. Maybe that's what they were referring to; maybe they have a different issue.

scq 4y ago

Firefox for Android used to implement scroll coasting in a way that felt very different from Chrome and native Android apps. I just gave it a try now and it seems like they've fixed it, scrolling feels native now.

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 ago
Little 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 ago
  The settings page stretches correctly. The issue is with the webpages.
  - 29083011397778 4y ago
    I'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.