"Pull to refresh" improvements

mozilla-mobile / firefox-ios

Firefox for iOS

Mozilla Public License 2.0

12.15k stars 2.91k forks source link

"Pull to refresh" improvements #9701

Open SimonBasca opened 2 years ago

SimonBasca commented 2 years ago

User Problem

From comment https://github.com/mozilla-mobile/firefox-ios/issues/9118#issuecomment-999681834 it seems that some user might accidentally refresh the page while on a login form which can cause a bad user experience.

Ideas for Solution

We could add a button to disable this option or we should improve the way this feature works.

┆Issue is synchronized with this Jira Task

gutley commented 2 years ago

Personally I can see no difference between FF and Safari in this. Not sure this warrants any changes. We 'could' run some JS before pull to refresh kicks in to see if there are any non-empty text fields on the page and offer the choice on whether to refresh, but I'm not convinced this needs another preferences option.

shttrstckak commented 1 year ago

Just a note as a user I am actually going to stop using Firefox iOS because this happens quite frequently, especially when scrolling back up to proof read long messages it will trigger. It is not worth the frustration of losing lengthy work typed on a virtual keyboard with two thumbs to continue using this browser.

Prurite commented 1 year ago

Just tested on ipad. The page starts refreshing immediately when pulled beyond a certain distance, which may be quite undesirable if it was triggered accidentally. Changing it to refresh on release (as many other browsers do) will be better, as if the user realizes that (s)he has pulled too far, (s)he can pull back and stay.

sryze commented 8 months ago

Yes please, I too would like to be able to disable this "feature" because it often gets triggered when I don't expect, e.g. when I scroll up on YouTube and it accidentally refreshes, I lose the recommendations. I prefer to use the Refresh button manually.

ocontant commented 8 months ago

The pull to refresh is the most undesirable features of modern mobile browser.

The implementation fail the basic UX principle:

Unpredictability (it triggers involuntarily, based on invisible to the user treshold)
No Trigger Validation, with a way to revert back
In forms, this is a destructive event, and there's no confirmation action.
No toggle button to disable it.

Sometime a form will take 80% of the screen and you need to scroll to see referential context hidden by the form, and trying to scroll up will trigger involuntarily the refresh.

Is there a plan to fix this, or provide a toggle button, or even a plugin?

My biggest pain at the moment is the ChatGPT webpage on IOS Firefox. It's a painful and frustrating experience.