Imagine UI design so bad that the same finger movement has two different outcomes.
This is actually request to remove a feature, or, more accurately, an anti-feature.
Please explain why your feature request fall into the scope of ungoogled-chromium?
In 2015, Google introduced the pull-to-refresh bug to their mobile Chromium and Chrome browsers, but it was optional, so everyone was happy.
But like any tumor that is not stopped soon enough, it will grow.
In 2019, Google made the pull-to-refresh gesture mandatory in Chromium/Chrome, and stood by their bad decision even after people have repeatedly and repeatedly and repeatedly complained about it causing accidental refreshes.
If this many people complain about it, perhaps there is a good reason for it. And that good reason is that it causes refreshing accidents and forces users to scroll carefully to avoid them, which itself is annoying.
Either the complaints didn't go through Google's thick skull, or Google refused to reverse this terrible decision probably to avoid the embarrassment of admitting failure on such a massive scale.
The damage extended to other chromium-based projects such as Kiwi browser.
Enough battery charge, enough cellular data, and most importantly, enough hours of life have been wasted to accidental refreshes. Enough hours have been wasted to having to rewrite a text after an accidental refreshing. Enough hours have been wasted to scrolling up at a slow speed to avoid accidentally refreshing after hitting the top of the page.
Even Google themselves admit that accidental refreshes are a possibility!
For situations like the Twitter PWA, it might make sense to disable the native pull-to-refresh action. Why? In this app, you probably don't want the user accidentally refreshing the page.
Indeed, but not only those situations. On all web pages, the existence of pull-to-refresh is a threat of accidental refreshing.
overscroll-behaviour:contain is useless because you can't edit the CSS on over 99.999% of websites in existence.
Pull-to-refresh is triggered by the exact same finger movement that scrolls up the page, so repeating this finger movement one time too much causes an unwanted refresh, making pull-to-refresh a poor design choice.
Please describe the feature you would like to have
A simple toggle in the settings would do.
Freedom from pull-to-refresh would incentivize people to switch to ungoogled-chromium. Pull-to-refresh has no place in a web browser. Pull-to-refresh is one of the worst creations by Google. Please kill it with fire. Thanks.
Describe the solution you'd like
Redundant to last section.
Describe alternatives you've considered
Firefox and Samsung Internet already provide the user the option to turn pull-to-refresh off, but they lack a different important feature: The ability to save pages as MHTML files. Firefox can only save pages as PDF (useless), Samsung Internet saves pages in the locked-in /data directory that can not be backed up or moved to a new device (even worse), except if the user has root access.
Mozilla developers refused to put saving pages as HTML/MHTML in their browser, so I don't expect it to be implemented anytime soon, even though the desktop version has it for decades.
Samsung Internet is a closed-source project with no public bug trackers, and I don't expect Samsung to respect the wish of implementing it from the feedback form.
Pull-to-refresh is one of the worst design choices ever made.
HT-7 changed the title
Imagine UI design so bad that the same finger movement has two different outcomes.
This is actually request to remove a feature, or, more accurately, an anti-feature.
Please explain why your feature request fall into the scope of ungoogled-chromium?
In 2015, Google introduced the pull-to-refresh bug to their mobile Chromium and Chrome browsers, but it was optional, so everyone was happy.
But like any tumor that is not stopped soon enough, it will grow.
In 2019, Google made the pull-to-refresh gesture mandatory in Chromium/Chrome, and stood by their bad decision even after people have repeatedly and repeatedly and repeatedly complained about it causing accidental refreshes.
If this many people complain about it, perhaps there is a good reason for it. And that good reason is that it causes refreshing accidents and forces users to scroll carefully to avoid them, which itself is annoying.
Either the complaints didn't go through Google's thick skull, or Google refused to reverse this terrible decision probably to avoid the embarrassment of admitting failure on such a massive scale.
The damage extended to other chromium-based projects such as Kiwi browser.
Enough battery charge, enough cellular data, and most importantly, enough hours of life have been wasted to accidental refreshes. Enough hours have been wasted to having to rewrite a text after an accidental refreshing. Enough hours have been wasted to scrolling up at a slow speed to avoid accidentally refreshing after hitting the top of the page.
Even Google themselves admit that accidental refreshes are a possibility!
Indeed, but not only those situations. On all web pages, the existence of pull-to-refresh is a threat of accidental refreshing.
overscroll-behaviour:containis useless because you can't edit the CSS on over 99.999% of websites in existence.Pull-to-refresh is triggered by the exact same finger movement that scrolls up the page, so repeating this finger movement one time too much causes an unwanted refresh, making pull-to-refresh a poor design choice.
Please describe the feature you would like to have
A simple toggle in the settings would do.
Freedom from pull-to-refresh would incentivize people to switch to ungoogled-chromium. Pull-to-refresh has no place in a web browser. Pull-to-refresh is one of the worst creations by Google. Please kill it with fire. Thanks.
Describe the solution you'd like
Redundant to last section.
Describe alternatives you've considered
Firefox and Samsung Internet already provide the user the option to turn pull-to-refresh off, but they lack a different important feature: The ability to save pages as MHTML files. Firefox can only save pages as PDF (useless), Samsung Internet saves pages in the locked-in
/datadirectory that can not be backed up or moved to a new device (even worse), except if the user has root access.Mozilla developers refused to put saving pages as HTML/MHTML in their browser, so I don't expect it to be implemented anytime soon, even though the desktop version has it for decades.
Samsung Internet is a closed-source project with no public bug trackers, and I don't expect Samsung to respect the wish of implementing it from the feedback form.
Pull-to-refresh is one of the worst design choices ever made.
Please nuke pull-to-refresh from the orbit, just to be sure.