-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request/Bug] disable pull down to refresh #4854
Comments
Thank you for opening an Issue in our Repository. |
Thanks for the report, would you be able to share a website where this can be reproduced? |
Uh yeah it happens most frequently with compcon.app
…-------- Original Message --------
On 8/5/24 7:43 AM, Marcos wrote:
Thanks for the report, would you be able to share a website where this can be reproduced?
—
Reply to this email directly, [view it on GitHub](#4854 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BDIXXZV3ZHWUP7H6WYKVIW3ZP5XQNAVCNFSM6AAAAABL66G6ZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYHE4DMMJXG4).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hello everyone :) |
Same. It's a nightmare to have this feature. There should be an option to disable pull to refresh just like in Firefox. Any site, let's say Duck.ai for example, you do a lot of chatting and scroll up to see something in the top and accidentally scroll a little more, now the page will start refreshing and you will loose everything till now. |
Describe the bug
My web pages will often refresh due to the pull down to refresh feature when I'm using web pages with scroll features (either the app does it when I'm trying to scroll, like a bug, or I just get to the top of the scroll and I refresh).
If we could get an option to disable it (because I find it more annoying than useful) that would be swell.
How to Reproduce
Expected behavior
I want it to stop refreshing pages on pull altogether, but fixing the refresh big would be fine I suppose.
Environment
The text was updated successfully, but these errors were encountered: