I would not be happy with mouse pointer hijacking. Seems to belomng in the same territory as scroll-hijacking but worse. The example case here could have been served by simply highlighting the area of interest in the UI with a red circle or a flashing pointer, whatever does the trick -- even though that may be distracting too.
There are a lot of interactions on a PC where user inputs land in the wrong place.
Claude Code and Codex in their various avatar allow us to type the next prompt while the aget is still working and responding on the earlier one. But this constantly runs into a permission prompt from running session -- either interrupting or worse entering a response to the permission prompt unintentionally. Even during normal prompting slash commands interfere annoyingly with normal use of the slash key (i use a slash to indicate a list of two or more choices sometimes when i write).
Permission popups and confirmation dialogs that appear unexpectedly and swallow our keystrokes, spacebar and enter key hits mid sentence have always annoyed me.
Laggy devices, and resource hungry sluggish UIs compound this problem.
Software moving the mouse cursor is only acceptable when the window is full-screen. If the user makes an application go full-screen, they are opting out of the normal desktop UI conventions. It's expected that full-screen software completely takes over the UI, and there are legitimate uses for moving the mouse cursor in full-screen software, e.g. centering an invisible cursor every frame in a first-person shooter game so endless view rotation is possible. But if it's windowed then it should be impossible.
> But if it's windowed then it should be impossible.
I worked on several apps for the visually impaired that automatically move the mouse cursor to different UI elements in the front-most application, regardless of the window state. It’s a good reminder that “impossible” often just means “I haven’t accounted for that use case yet.”
If it's part of the OS's standard accessibility framework then it's acceptable. The important point is that applications shouldn't be able to arbitrarily move the mouse in situations when it's unexpected.
The effort put into making sure you know how to turn this feature on makes me question why it's so important to them, is the 3rd party paying them for this data?
Even major features in Adobe apps the furthest they go is those video popups rendered using webviews so they glitch into existence as a white box.
I would not be happy with mouse pointer hijacking. Seems to belomng in the same territory as scroll-hijacking but worse. The example case here could have been served by simply highlighting the area of interest in the UI with a red circle or a flashing pointer, whatever does the trick -- even though that may be distracting too.
There are a lot of interactions on a PC where user inputs land in the wrong place.
Claude Code and Codex in their various avatar allow us to type the next prompt while the aget is still working and responding on the earlier one. But this constantly runs into a permission prompt from running session -- either interrupting or worse entering a response to the permission prompt unintentionally. Even during normal prompting slash commands interfere annoyingly with normal use of the slash key (i use a slash to indicate a list of two or more choices sometimes when i write).
Permission popups and confirmation dialogs that appear unexpectedly and swallow our keystrokes, spacebar and enter key hits mid sentence have always annoyed me.
Laggy devices, and resource hungry sluggish UIs compound this problem.
Software moving the mouse cursor is only acceptable when the window is full-screen. If the user makes an application go full-screen, they are opting out of the normal desktop UI conventions. It's expected that full-screen software completely takes over the UI, and there are legitimate uses for moving the mouse cursor in full-screen software, e.g. centering an invisible cursor every frame in a first-person shooter game so endless view rotation is possible. But if it's windowed then it should be impossible.
> But if it's windowed then it should be impossible.
I worked on several apps for the visually impaired that automatically move the mouse cursor to different UI elements in the front-most application, regardless of the window state. It’s a good reminder that “impossible” often just means “I haven’t accounted for that use case yet.”
If it's part of the OS's standard accessibility framework then it's acceptable. The important point is that applications shouldn't be able to arbitrarily move the mouse in situations when it's unexpected.
vim-athena would automatically move your cursor towards the command buttons whenever it made a popup appear
i thought that was genius, until i upgraded to vim-motif, which would instead move the popup to where your mouse cursor is
Windows has a “snap to default button“ setting which does the same.
Saves you a bit of movement on large screens, but since it jumps it doesn’t lead the eyes which makes is disorienting.
In the early days it was pretty common to move the pointer to the active element when one started navigating with the keyboard.
But yeah, it feels like somebody physically grabbing your hand and moving it.
The effort put into making sure you know how to turn this feature on makes me question why it's so important to them, is the 3rd party paying them for this data?
Even major features in Adobe apps the furthest they go is those video popups rendered using webviews so they glitch into existence as a white box.