When a mouse event is dispatched to an OOPIF target through DevTools Input.dispatchMouseEvent command, the x and y coordinates for the event target are interpreted differently depending on the platform:

* On desktop, the x and y coordinates are interpreted relative to the upper-left corner of the frame.
* On Android, the coordinates are interpreted relative to the upper-left corner of the screen.

Not sure what's causing the difference, but the interpretation should be consistent on all platforms. This difference currently requires special casing in ChromeDriver.