Confirmed on kiosk-entryway: chromium's built-in cursor autohide behavior in kiosk mode doesn't actually hide the mouse pointer, unlike assumed.
Follow-up: add a service (likely `ydotool`-based, since Wayland's security model blocks clients from repositioning the global cursor directly - `ydotool` works around this via `/dev/uinput` at the kernel level) to move the cursor to the bottom-right corner on kiosk hosts (`kiosk-gene-desk`, `kiosk-entryway`), out of the way of the dashboard content.
Needs its own privileged `ydotoold` daemon with uinput access, and the actual resolution as the compositor sees it post-rotation to compute the target coordinates correctly.
Confirmed on kiosk-entryway: chromium's built-in cursor autohide behavior in kiosk mode doesn't actually hide the mouse pointer, unlike assumed.
Follow-up: add a service (likely `ydotool`-based, since Wayland's security model blocks clients from repositioning the global cursor directly - `ydotool` works around this via `/dev/uinput` at the kernel level) to move the cursor to the bottom-right corner on kiosk hosts (`kiosk-gene-desk`, `kiosk-entryway`), out of the way of the dashboard content.
Needs its own privileged `ydotoold` daemon with uinput access, and the actual resolution as the compositor sees it post-rotation to compute the target coordinates correctly.