Re: [w3c/gamepad] Should spec a buffering/refresh interval model of gamepad data? (#22)

kvnloo left a comment (w3c/gamepad#22)

Current Chromium adds an important new data point to this discussion.

`GamepadProvider` still polls at `4 ms` (~250 Hz), but it now detects changes between consecutive samples and sends `GamepadRawInputChanged` for button, axis, and touch changes.

So Chromium effectively has both models now: shared-memory snapshots for `getGamepads()` and an event path for changes.

That seems like a useful basis for specifying the intended hybrid model rather than choosing polling or events exclusively.


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

Message ID: <w3c/gamepad/issues/22/5941893285@github.com>