RFR: 8150564: Migrate useful ExtendedRobot methods into awt.Robot [v9]

[Damon Nguyen]

On Mon, 3 Nov 2025 19:08:30 GMT, Sergey Bylokhov <serb at openjdk.org> wrote:

> I don’t think it will be possible to change the implementation once these methods start being used by the tests, as the tests will depend on their behavior in one way or another. This means that once we release these methods, their implementation will essentially be set in stone. It would be better to check how this is implemented in a different API and see how difficult it would be to adjust the current implementation to follow the same behavior.

I don't see why it wouldn't be possible to make changes to the implementation of the mouse movement. I have already looked at the API you described for mouse movement, and the implementation there is not too different. I don't think I'd need any new parameters or variables (except for 2 constant int vars), and would instead just change the calculation for the loop. For any relevant tests, it seems as long as the mouse can move from point A to B in a non-skipping fashion, then the implementation should be fine.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26969#issuecomment-3492402655