Aha! Confirmed on arale with a USB mouse and mir-demos.
Relative motion events usually work continuously, and come in even after the cursor hits the screen boundary. However Mir stops sending relative motion events if you've rotated the screen (touch+volume key in mir_proving_server) and the cursor happens to be outside of the original non-rotated dimensions. That's a Mir bug.
Aha! Confirmed on arale with a USB mouse and mir-demos.
Relative motion events usually work continuously, and come in even after the cursor hits the screen boundary. However Mir stops sending relative motion events if you've rotated the screen (touch+volume key in mir_proving_server) and the cursor happens to be outside of the original non-rotated dimensions. That's a Mir bug.