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.
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.”
That is quite a different statement from "It should be impossible." What should be impossible is for the OS to prevent this type of usage when it is clearly useful. Outside of accessibility, I use these features to automate native macOS GUI app testing.
In 25 years of developing software for Windows and macOS, I cannot recall a single instance of the mouse cursor moving unexpectedly.
Saves you a bit of movement on large screens, but since it jumps it doesn’t lead the eyes which makes is disorienting.
i thought that was genius, until i upgraded to vim-motif, which would instead move the popup to where your mouse cursor is
But yeah, it feels like somebody physically grabbing your hand and moving it.
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.