Dragging clickable element breaks click in general
tmvkrpxl0 opened this issue · comments
Description
If I drag any clickable element, Brave no longer responds to click
Steps to Reproduce
- Go to random website
- Drag element
- It's now unusable
Actual result:
2024-05-14.14-28-15.mp4
Expected result:
It should work normally
Reproduces how often:
Easily reproduced, It happens always.
Too easy in fact I sometimes do this accidentally while clicking.
Brave version (brave://version info)
Brave: 1.65.132 Chromium: 124.0.6367.202
Revision: ef7b9d19db96d7f4363674bbcd02b74c5f055091
OS: Linux
Version/Channel Information:
- Can you reproduce this issue with the current release?
Yes - Can you reproduce this issue with the beta channel?
Yes - Can you reproduce this issue with the nightly channel?
Untested
Other Additional Information:
It used to be fine on x11, this started to happen after I switched to wayland.
- Does the issue resolve itself when disabling Brave Shields?
No, but irrelevant. - Does the issue resolve itself when disabling Brave Rewards?
Untested, but irrelevant as well. - Is the issue reproducible on the latest version of Chrome?
Miscellaneous Information:
I always launch brave with those flags:
brave-browser --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime
In the video, after I dragged, the mouse is stuck in "hold"
I am clicking various element but it doesn't register
I misread issue template and answered wrongly: it doesn't fix itself when I disable shield.
@tmvkrpxl0 Are you still seeing an issue with our latest release 1.66.110?
Something you might try @tmvkrpxl0 is to visit brave://settings/appearance and then try changing what is used. So you can pick GTK theme for example. This might not fix the issue - but worth a try. You can try changing the value to different settings and please let us know
@tmvkrpxl0 Are you still seeing an issue with our latest release 1.66.110?
1.66.110 is not yet available on stable channel for me yet. I instead tested with beta channel whose version is higher. It works fine there now. so I think it's resolved?
I hava that exact same issue as well, im on kde arch and it only happens when using wayland