Status Update
Comments
po...@gmail.com <po...@gmail.com> #2
I agree. You're absolutely right.
Everyone is in trouble: https://support.google.com/chrome/thread/8152831?hl=en
Everyone is in trouble:
rs...@chromium.org <rs...@chromium.org> #3
[Empty comment from Monorail migration]
va...@chromium.org <va...@chromium.org> #4
[Empty comment from Monorail migration]
va...@chromium.org <va...@chromium.org> #5
Thanks for filing the issue!
@jinsukkim/@bokan: Is this something intentionally changed due to https://crbug.com/chromium/974823, Please help in providing more inputs.
[Monorail components: -UI UI>Browser>PullToAction]
@jinsukkim/@bokan: Is this something intentionally changed due to
[Monorail components: -UI UI>Browser>PullToAction]
ji...@chromium.org <ji...@chromium.org> #6
Sorry for the trouble. The fix already landed at 76.0.3809.48
https://chromium.googlesource.com/chromium/src.git/+/d71e9f929000bd608d514ad187b6ae04dd9b646d
ww...@gmail.com <ww...@gmail.com> #7
Nope, "fixing" the aggressiveness of the unwanted feature does not count as a "fix" for this missing setting! We want a way to turn off this obnoxious & unnecessary gesture; not a modification to how it works. Please restore the "disable pull-to-refresh" flag.
This is NOT a duplicate of any issues with pull-to-refresh triggering at the wrong times. This issue is that the flag to disable it has been removed. If the flag won't be restored, don't merge this issue with one about issues with P2R, just be honest & label it "will not fix" IE "ignored".
This is NOT a duplicate of any issues with pull-to-refresh triggering at the wrong times. This issue is that the flag to disable it has been removed. If the flag won't be restored, don't merge this issue with one about issues with P2R, just be honest & label it "will not fix" IE "ignored".
is...@google.com <is...@google.com> #8
This issue was migrated from crbug.com/chromium/984585?no_tracker_redirect=1
[Monorail mergedinto: crbug.com/chromium/974823]
[Monorail components added to Component Tags custom field.]
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
Description
Steps to reproduce the problem:
1. Spend tie and effort writing something on Android Chrome, inside of a text box on some website.
2. Accidentally pull down and refresh the site and lose your work.
3. Feel bad emotions because you lost your work. 😤😡
What is the expected behavior?
Ability to disable the "pull down to refresh" feature.
What went wrong?
The option to remove it was removed from chrome://flags in Chrome 75.
Did this work before? N/A
Chrome version: 75.0.3770.100 Channel: n/a
OS Version: OS X 10.14.3
Flash Version:
Please bring back the option to disable pull-down-to-refresh. It is highly annoying when a swipe-gone-wrong refreshes the page unintentionally.
I would much rather hit the menu button, then hit the refresh button. Then I have more control.
It is very easy for this mistake to happen when trying to scroll text fields, but instead accidentally refreshing the whole page.