Jun 17, 2019
Missing Android Chrome 75 flags disable-pull-to-refresh-effect How to disable it now?
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Last edited Jun 24, 2019
Jul 3, 2019
Thanks for posting and for the feedback about this change. As another user I appreciate things like this can be frustrating, so if this is important to you, I’d encourage you to also send this feedback to Google from within the Chrome menu so your feedback is recorded there too. Please be aware that you may not receive a response, however the team are still reading the feedback! To review the feedback you have sent across all Google products, visit the Google Feedback site.
(I'm going to mark this post a recommended answer to this topic. This is the best way for this forum system to display an important update at the beginning of a thread, and I want to help ensure that those new to the discussion see the latest update).
Last edited Jul 6, 2019
Product Expert Alumni david.king recommended this
Helpful?Upvote Downvote
All Replies (228)
Jun 17, 2019
Last edited Jun 18, 2019
Jan 17, 2020
Jan 21, 2020
Jan 21, 2020
Saying "tell google" does not help or offer a viable solution.
I hate when supposed experts inflate their numbers by copy and pasting a generic "solution"
to every query they can.
It has almost four times as many down votes as up yet remains at the top, WHY???
Jan 22, 2020
Easy fix guys if you using web-app that you control
like
...
<meta name="mobile-web-app-capable" content="yes">
... in you page
<style>
body{
overscroll-behavior-y: contain;
}
</style>
but still if it is possible to disable it overall it would be great!!!
Google user
Jan 23, 2020
Last edited Jan 23, 2020
Feb 3, 2020
There was literally no reason to remove this flag. I'm quite sure a relative few used the option because nobody knew it was there!
I GUARANTEE there would have been many more users who took advantage of killing pull to refresh if the option was properly available in the Chrome Settings menu. Normal users are never found digging into the flags menu.
Thanks Google. Another stooopid user-hostile design change. Another reason to use another browser.
Last edited Feb 3, 2020
Feb 5, 2020
Feb 14, 2020
Chrome 63 has added a css property to help out with exactly this. Have a read through this guide by Google to get a good idea of how you can handle it.
Here is their TL:DR
The CSS overscroll-behavior property allows developers to override the browser's default overflow scroll behavior when reaching the top/bottom of content. Use cases include disabling the pull-to-refresh feature on mobile, removing overscroll glow and rubberbanding effects, and preventing page content from scrolling when it's beneath a modal/overlay.
To get it working, all you have to add is this in your CSS:
body {
overscroll-behavior: contain;
}
Mar 11, 2020
You created an artifical problem and propose an ugliest way to fix it.
Just give user a way to disable the accidential refresh "feature"
Mar 13, 2020
Mar 28, 2020
Last edited Mar 28, 2020