Chromium

[Empty comment from Monorail migration]

Thanks for filing the issue!

This seems to be similar to https://bugs.chromium.org/p/chromium/issues/detail?id=974823, hence merging into it and marking it as Duplicate.
Please feel free to undupe if not the case.

Unfortunately I'm not allowed to view the https://crbug.com/chromium/974823. Can it be made public?

This issue has been merged with one that is not viewable. Are we to presume no further feedback or reporting of this issue is desired? Why is the other topic not public in the first place?

Feels like Google is trying to push this obviously important issue under the rug. Please follow up here, since https://crbug.com/chromium/974823 is not accessible to public.

At bug https://bugs.chromium.org/p/chromium/issues/detail?id=984585 (also duplicated of the private https://crbug.com/chromium/974823), says it has ben fixed at 76.0.3809.48 (released on the beta channel, not yet on stable).

Unfortunately, 984585 is NOT a duplicate of this issue. OP of 984585, like myself (& like so many other complainants) wants the flag to DISABLE pull-to-refresh restored to the chrome://flags menu. THIS bug (980032) relates to problems with how pull-to-refresh works, but 984585 relates specifically to the fact that this unwanted, unnecessary, ill-conceived "feature" is on by default & can no longer be turned off!

Frankly, all these additional one-finger one-direction gestures are annoying usability killers: Swiping with one finger is already taken for scrolling; A multi-touch or rotational gesture would be more appropriate for triggering seldom needed actions like Refresh.

I'm real happy that the issue of accidental triggering may soon be fixed for whatever Twitter addict was unable to find the Refresh button before pull-to-refresh was implemented, but the fact that 984585 has been merged with issues that it CLEARLY is NOT a duplicate of, & further, the fact that the issue it was merged with is not publicly accessible, both strongly indicate to me that Google has no intention of restoring our ability to disable this overly simplistic gesture.

Fixed the accidental triggering? Great, post that HERE; but don't miscategorize the wholly separate issue that THE METHOD OF TURNING THIS GESTURE OFF HAS BEEN REMOVED as being the same thing. 984585 is not a duplicate of this issue & 984585 is NOT resolved until the off-switch for this (stupid!) gesture has been restored.

This issue was migrated from crbug.com/chromium/980032?no_tracker_redirect=1

[Monorail mergedinto: crbug.com/chromium/974823]
[Monorail components added to Component Tags custom field.]