Please add a toggle to disable the pull-down-refresh.
Reason: It is annoying, pages keeps refreshing whenever I swipe down
More than just annoying. I just lost a large post to Reddit because the page reloaded.
2 Likes
YES PLEASE It is way beyond annoying. At least an option to turn it off.
1 Like
Been a while since I used Android. Are you sure there’s no setting for that anywhere? I’m wanting to say I had it disabled long ago on my Samsung Galaxy S9.
In any case, I do know it’s an option on iPhone, as you can see in the screenshot below. So if it’s not on Android, might be something to come here for the future
Yes! Upvoted. It happened to me too many many times, cumulatively lost literally hours of work. I’m just thinking a better solution would be a delay. Like you have to already be at the top of the page for a second or half for refresh on next pull-down. Better yet, have a Refresh on Pull-down Behaviour setting as a select input with the options being Disabled, Delayed, Single pull-down, Double pull-down.
@Saoiray no setting on Android
1 Like
I lose at least one long post a week in Brave and it’s probably pushing me to go back to Chrome where I have an add-on (Formalizer?) that keeps what I type in any edit window. In brave I only navigate away and when I come back the text often disappears in from of my eyes and I don’t know if a way to either get it back or find it in summer cached file: What’s the solution? I don’t want to go to a separate editor to your every response on a forum - that seems to be the only option other than using chrome. It’s bloody annoying.
1 Like
This just happened to me - lost 30 mins of work, then came here and found all the other people who already been flagging this as a problem with Brave for over a year at least now! What on earth is going on? How can something so glaringly obviously bad, not have been fixed yet? It’s rage-inducing. I was actually thinking Brave might be the browser that could finally convert me away from Firefox. I love it, features, privacy, performance, everything. Then this happens and I find it’s causing misery for so many others, and is well-documented, and now despite how much I like Brave and would probably use most of its services tbh, given time, I will actually fully uninstall it across Android, Windows and Linux, and stay on FF, if this one issue is not fixed. Because suddenly I feel like I’m losing faith. This is basic good UX. It’s not a complicated argument. It’s not hard to understand the problem. And if you have ever lost anything data-wise (which is most people, incl. Brave devs, I’d imagine) and you have empathy, you would see these reports and hopefully empathy would kick in, you’d recall the last time you lost something because of an unintentional page refresh, and the recollection of what that moment felt like should, ideally, cause you to feel your users’ pain, and resolve to help them immediately. Unless something is lacking. I’d hope it’s neither empathy nor respect for its users because these seem to be things that are kinda baked into the Brave identity, ostensibly. Yet here we are - all these annoyed users, all these community reports and threads elsewhere (all over Reddit too) with, say, a year or so gone by on a lot of them, and look - it’s still happening to bright-eyed optimistic potential Firefox converts (and you know we’re the most difficult bunch of browser users to shift because of how conscientious we broadly tend to be about choosing, deliberately, the browser we use, based on something kinda intentful and vaguely moral). If Brave is already appealing to privacy- and security-conscious users like me, and tempting us away from FF (which no browser has ever managed to do, personally) then they have a lot to feel positive about… IF they decide not to squander that trust and good faith by not addressing comprehensible, long-standing, inexpensively- and easily-fixed, high-user-friction pain points. Thinking about the other browsers I’ve used, I don’t think ‘pull down to refresh’ is in some of them, but even where it is, I don’t recall its being mandatory? And where it is present, it’s not always on by default. So Brave seems to have not only turned on by default and made mandatory a minor feature that most browser companies have either chosen not to implement, or if they have, haven’t turned on by default, and certainly haven’t made ‘always on’). Brave has ALSO then sat back and seemingly just… ignored the plethora of unhappy Android users all over the web with stories of woe explaining how it’s caused them to lose work, or had a personal or creative cost, and ignored the explanations of why it’s problematic, and ignored the well-known principle of it being good business sense to fix things which are low cost in terms of dev time while also high-cost in terms of user pain/friction. Those are the low-hanging fruit - low cost fixes which resolve big user pain points, so result in high positive sentiment and user loyalty for minimal dev time/money invested. They are quick wins. Sensible companies know this strategy. And conversely, when brands don’t enact the quick fixes, the more time passes without them being addressed, the more additional friction, frustration and confusion accumulates in the user base on top of the inital issue. Users start to wonder if the brand actually just doesn’t care about their issue. And that is a bigger problem. Apathy and disillusionment set in, and you start losing your user base, and ironically, because you didn’t strategically remedy something in the short term, which would have cost you very little, and would have carried long-term benefits for the business. I would love to see it fixed. I’m going to stick around a few days/weeks and keep my fingers crossed, and if there’s still nothing but inertia and stony silence, I will wave a sad farewell to this Brave new world.
Sure, adding a toggle to disable the pull-down refresh feature would be a great way to improve user experience, especially for those who find it disruptive. This would allow users to choose whether they want the refresh option enabled or not.