Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15)

> solves the most important use case--missing button presses that happen between polls.

Gamepad button (and axis) events are also important for applications that do not process inputs locally; i.e., when button and axis state is streamed to a remote service that manages the application state, waiting until rAF time to handle inputs adds a significant amount of input latency. Firing events for these inputs would allow the state to be streamed more quickly after the device is polled.

-- 
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/gamepad/pull/15#issuecomment-399531973