cursor disappearing/getting stuck in different states #43824
Labels
bug
Chromium/waiting upstream
Issue is in Chromium; we'll likely wait for the fix
feature/user-interface
All UI related
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
QA/Yes
release-notes/include
Description
We're getting reports via https://www.reddit.com/r/brave_browser/comments/1ijxkxq/mouse_cursor_sometimes_doesnt_appear_at_all_or_is that users are also running into the issue that I've experienced a few times with
C133
onWin 11 x64
. Originally, I thought it could be related to https://www.windowslatest.com/2025/02/05/windows-11-kb5050094-has-major-issues-including-spinning-cursor-on-windows-11-24h2 but looks like it's most likely an issue that was introduced withC133
.When using Brave, sometimes the mouse cursor just "disappears" or gets stuck in different states. For example, these are the cases that I've ran into so far in the last few days on
Nightly
withC133
:link pointer
cursor when it should be the regular cursorUsually when the above happens, you need to restart Brave to get the cursor back. Sometimes switching to another application and returning to Brave helps but not always.
Steps to reproduce
Unfortunately there's no STR/Cases as this is pretty difficult to reproduce. I've personally only ran into this ~3-4 times but don't know why/how it occurred. Tried a few things but had no success getting STR/Cases. Hopefully someone from https://www.reddit.com/r/brave_browser/comments/1ijxkxq/mouse_cursor_sometimes_doesnt_appear_at_all_or_is can help with STR/Cases.
Actual result
As mentioned above, there's a few cases that are occurring (at least these are the scenarios that I've experienced/ran into)
link pointer
cursor when it should be the regular cursorExpected result
Mouse shouldn't be disappearing/getting into "stuck" states when using Brave.
Reproduces how often
Easily reproduced
Brave version (brave://version info)
Channel information
Reproducibility
Miscellaneous information
No response
The text was updated successfully, but these errors were encountered: