Here is a screen capture of the example code from the first post, running on Windows:
And here is the same setup running on MacOS:
As you can see, on Windows the cursor is being warped properly the second time as well. On MacOS, as the position is determined by an offset from the current cursor coordinates, the second click doesn’t warp the cursor, indicating that the cursor’s position is not set internally.
Based on the following thread: Mouse.WarpCursorPosition() produces mouse delta on Linux but not on Windows?
I suspect that this issue is also present in Linux, and only works correctly on Windows (if reporting the new position as the cursor’s position is the intended behaviour).
The following thread appears to report the same issue back in version 1.0.0 for Windows: InputSystem reporting wrong mouse position after WarpCursorPosition
The solution the author of the thread proposes doesn’t seem to work in my situation.
Any help, workaround or suggestion is greatly appreciated!