MouseMotion delta is position instead of delta

[mentics]

Using Bevy 0.8.1. Ran the mouse_input_events example on Windows 10, Windows 11, and WSL2 on that Windows 11, all with similar results.
Reproduce:
clone Bevy, checkout latest, run: cargo run --example mouse_input_events
Some output:

2022-10-27T05:18:38.149400Z  INFO mouse_input_events: MouseMotion { delta: Vec2(1555.0, 872.0) }
2022-10-27T05:18:38.149441Z  INFO mouse_input_events: MouseMotion { delta: Vec2(1528.0, 865.0) }
...
2022-10-27T05:19:55.403036Z  INFO mouse_input_events: MouseMotion { delta: Vec2(2555.0, 1353.0) }
2022-10-27T05:19:55.403076Z  INFO mouse_input_events: MouseMotion { delta: Vec2(2559.0, 1366.0) }
2022-10-27T05:19:55.416493Z  INFO mouse_input_events: MouseMotion { delta: Vec2(2559.0, 1379.0) }
2022-10-27T05:19:55.416537Z  INFO mouse_input_events: MouseMotion { delta: Vec2(2559.0, 1391.0) }
...
2022-10-27T05:21:58.745255Z  INFO mouse_input_events: CursorMoved { id: WindowId(00000000-0000-0000-0000-000000000000), position: Vec2(0.0, 9.0) }

Funny thing is that in the above example (Win 11 WSL2), they're screen coordinates, not window coordinates. CursorMoved events are window coords, which is what I would expect.

Is there a bug somewhere or is there some config or something that I missed? I assumed that MouseMotion.delta would be a delta from the last event, not coords, and the code I've seen that uses it seems to assume that is the case.

Update: ok, it gets weirder: win 10 now seems like it might be working (not sure what changed), win11 follows full screen but from 0 to 65536 for both x and y, and win11 wsl2 gives the above.

Update: So, this probably isn't Bevy specific. I just grabbed https://github.com/rust-windowing/winit and ran cargo run --example cursor_grab and it showed the same behavior.

[mentics]

Found a bug already filed for winit for the WSL2 case: Windows WSL2 GUI MouseMotion returning position instead of delta

And the Windows 11 case is because I was accessing that computer remotely via Parsec. If I run the test directly on the machine, the delta looks ok. So, I created an issue on winit for that case.