Beautiful privacy. Brave 1.81.137, Chromium 139.0.7258.158 is good for me. when i use higher version of brave and click and hold on a webpage, not on a link, i always get a menu (Download, share, print). So i can’t use YouTube Player to fast forward the video on mobile page. Thank you for making privacy working in Android.
@D.a.n please update your browser. This issue existed a month ago and was fixed. The current version of Brave on Android is 1.82.166 and the issue should not happen there.
Hello Stephen, thank you for your answer. I just updated brave.
I updated to Brave 1.82.166, Chromium 140.0.7339.133 and now it happens again.Stephen, are you able to view the screenshot?
A new menu disrupts the function of the videoplayer.
My Android devices and reports from others were that it’s fixed. So I’m not sure what issue you might be having unless you might have modified flags or something? It’s a bit weird.
Github for the issue was https://github.com/brave/brave-browser/issues/48395
Back then I did find that if you enabled #enable-empty-space-context-menu-clank in brave://flags then the issue occurred as you see. But the fix should have resolved. You could always go to Disable that.
Questions:
- What device are you using?
- What version of Android are you on?
- You’re saying you have now updated Brave?
- C3pPro Android 14.
- In my case, without any flags, never used, it happens after 181.137 to 182.166.
- So, since then i downgraded brave first time in my life. On my Phone 182.166, chromium 140.0.7339.133 it works fine. Strange, only on my tablet, i have this issue, No flags.
1 Like
You may need to change that flag yourself for now and disable it, as you see in this screenshot
In the meanwhile, I’m going to tag @Serg and @Mattches to see if they have any ideas why yours wouldn’t be seeming to be getting the change they made.
1 Like
yes. You are right. Thank you. But why ist enabled as default on my tablet?
On my phone its disabled as default.
That flag was controlled via griffin study and changed the default value to Disabled till chromium 140. 1.82.166 switched it back to Default already and upstream should have fixed it by that point. It happened mostly on Samsung devices and we don’t see the issue there already. But it looks like some devices are still affected. I checked and upstream also have it Default already, hopefully they fix it soon.
2 Likes
Same here. I was also facing this issue for recent few updates
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.