Refresh by pulling down from the top of a page should be disable
Categories
(Firefox for iOS :: Browser, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| fxios | ? | --- |
People
(Reporter: jeremyleon, Unassigned)
Details
This feature has been nothing but frustration for me since it was introduced as default behavior last year. The worst part is that I never felt the need to use it for what it is, and even more so since the address bar is now at the bottom of the screen with the refresh button for me.
I have only experienced unwanted reloads for just under a year now. The worst situations being losing my text while typing or failing to authenticate payments due to accidental refreshes. Another downside is that it drains my battery faster as iOS has only shown me higher data and power consumption than ever with Firefox from the week it was introduced until now.
Came here to complain about the same thing. I'm a very fast scroller to go back to the top of a page, and I've lost a lot of forms and application state from scrolling past the top and Firefox Mobile engaging refresh. There are plenty of applications that use the pull down to refresh behavior, but the best ones provide a more clear visual indicator. The current light grey * is too subtle. Second, they typically require the user to pull down about half way down the screen. Third, they only activate if you pull down past the refresh point and release—like pulling back a rubber band and launching it—giving the user an opportunity to change their mind. So in summary, the current behavior engages too easily & without enough warning. It's been driving me crazy. Subscribed.
Another thing I feel like I've seen some apps do is not engage refresh if the scrolling speed is over some threshold. Keep in mind that on iOS, you can keep increasing the velocity of the scroll by flicking. And the distance of the "bounce back" when you hit the top is determined by the speed of the scroll. I'm pretty sure that if you scroll fast enough, you can scroll from somewhere in the center of a long page, get the velocity way up, and have it cross that small threshold by doing the normal bouncy animation by hitting the top, and engage refresh at the time time. Again, iOS scrolling is physics-based and the top and bottom are like shock absorbers. The more inertia you have, the more the page will bounce. If refresh is a fixed threshold amount, it's really easy to engage it unintentionally. As I said in my other comment, waiting for the user to pull down and release would probably solve this. Only refresh when you're scrolled down past the top and the user is still touching the screen and at the moment of release, the inertia is low.
Description
•