Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)

To the best of my knowledge, other OSes all provide a poll-based API for gamepad; Android is the only OS to issue events for it instead.

One other important detail is that the stick axis scrolling is a harder problem.  If the user snaps the stick to one extreme and then keeps it there, we only get one motion event, and then Chromium has to create a self-driven animation to scroll.  So something like the "beforescroll" event model would be a better fit if we want to provide fine-grained control over joystick scroll.  That said, coarse-grained disabling using "overflow: hidden" may be sufficient in practice anyway.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/79#issuecomment-218860801