When the cursor is captured by Minecraft and you use a 3-Finger swipe to get to another fullscreen application (e.g. Minecraft -> Browser) It works perfectly fine and like normal. for a second.
After ~1 Second the cursor snaps to a random position even though I am focused on the browser and not Minecraft,
After it teleports to the random position you can use it like normal.
It is usually a bit to the left of the center of the screen, but sometimes it’s a slightly above the center, all the way to the left, and basically everywhere.
Previous (Correct) behavior was the cursor staying in the center of the screen while swiping over, and then letting you use the cursor without the teleporting, Minecraft should not try to correct for this (which i assume is what it’s doing) and just leave the cursor in the center of the screen like before.
Environment
MacOS Tahoe 26.6.2, M5 Chip
Linked issues
is duplicated by 1
Attachments
Comments 6
The weird blurry rendering was fixed by selecting OpenGL, Hopefully that option is never deprecated
It also make the snap happen much quicker, It’s still there though, but slightly less annoying
OpenGL will be deprecated once Vulkan is in a stronger state. Regarding the issue itself, from what I’m able to tell it’s plausible that Minecraft may in fact be responsible for this behavior, even though in both our videos the blink happens once the swipe has completed and the other app is focused. Ideally macOS would not allow Minecraft to control the cursor under such circumstances, but since Minecraft may be doing so I will confirm this report, although I will edit the description to remove any mention of the “screen wobbling”, since that issue should be tracked separately. If you decide to re-report that issue (assuming no report for it yet exists), please upload another screen recording with that report which clearly shows the issue with F3 enabled, since I wasn’t actually able to notice that issue in the video you just provided.
For the screen wobbling, It’s not a major issue, I can ignore that for now until OpenGL is deprecated, Vulkan would be much more polished by then anyways.
When OpenGL is deprecated, if the issue is still there I will obviously need to file a bug report for that assuming nobody has already by then.
I also noticed that it wasn’t appearing in the recording, So I guess that narrows it down for someone who knows much more about that than me
Per MC-312285, this affects more than just macOS.
I believe I’m encountering the same issue in 26.3 itself on macOS Golden Gate 27.0.1, but just to be sure could you upload your own recording of the issue, with the debug screen (F3) enabled and showing the game version and system specs?