Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

rampant false positive pull down to refresh gesture

  • 2 replies
  • 6 have this problem
  • 3 views
  • Paskiausią atsakymą parašė simonmorgan73

more options

Firefox Nightly 110.0a1 (Build #2015925675), Sony Xperia 1 mk3, 61.2.A.0.382 release-keys Android 13

Been having issues with the refresh gesture, namely it activating when just trying to scroll up the page.

I'm not certain of the proper behaviour, but I've had pull down to refresh initiate with all kinds of downward swipes; fast, slow, short and long; and in various locations on the screen; centre, sides (close enough to also start back gesture), lower third; and even seen it wanting to refresh when simply tapping to stop inertia scroll, as well as when pressing and holding to keep screen alive for seconds before pulling down to return to the top.

Noticing it initiate, then releasing upward to cancel, then repeating the previous downward swipe intermittently triggers it again; sometimes it's gone, sometimes it triggers another once or twice, and one time it just would not stop and I couldn't scroll up the page no matter where on the screen I began to swipe down.

I'm presuming it's only meant to activate in upper third or even quarter, but regardless, this is a relatively recent (several days to a week, idk) issue that I'm dealing with, although it has become rife tonight.

Some websites seem better than others, and I was considering it was a fault of some designs, but alas I couldn't find any spots where I could consistently get it to happen; not even dragging from the top of the screen is working right now, so I have no idea what's going on.

https://ok2fly.com.au/ was a nightmare; tap anywhere to open a pop-up, scroll to bottom, then try to scroll up. I've got a great little screen record to demonstrate how inconsistent it is, if anyone wants.

Lemme know if there's anything else I can do to help diagnose this.

Firefox Nightly 110.0a1 (Build #2015925675), Sony Xperia 1 mk3, 61.2.A.0.382 release-keys Android 13 Been having issues with the refresh gesture, namely it activating when just trying to scroll up the page. I'm not certain of the proper behaviour, but I've had pull down to refresh initiate with all kinds of downward swipes; fast, slow, short and long; and in various locations on the screen; centre, sides (close enough to also start back gesture), lower third; and even seen it wanting to refresh when simply tapping to stop inertia scroll, as well as when pressing and holding to keep screen alive for seconds before pulling down to return to the top. Noticing it initiate, then releasing upward to cancel, then repeating the previous downward swipe intermittently triggers it again; sometimes it's gone, sometimes it triggers another once or twice, and one time it just would not stop and I couldn't scroll up the page no matter where on the screen I began to swipe down. I'm presuming it's only meant to activate in upper third or even quarter, but regardless, this is a relatively recent (several days to a week, idk) issue that I'm dealing with, although it has become rife tonight. Some websites seem better than others, and I was considering it was a fault of some designs, but alas I couldn't find any spots where I could consistently get it to happen; not even dragging from the top of the screen is working right now, so I have no idea what's going on. https://ok2fly.com.au/ was a nightmare; tap anywhere to open a pop-up, scroll to bottom, then try to scroll up. I've got a great little screen record to demonstrate how inconsistent it is, if anyone wants. Lemme know if there's anything else I can do to help diagnose this.

All Replies (2)

more options

Hi

Thank you for helping to test future versions of Firefox for Android by using the Nightly build. To file a bug report see File a bug report or feature request for Mozilla products for details.

more options

This is happening on the realease version too, not just nightly. It's actually making the browser unusable.