Re: [w3c/gamepad] Should fire events instead of using passive model (#4)

kvnloo left a comment (w3c/gamepad#4)

This no longer appears purely hypothetical in Chromium.

The current provider compares consecutive 250 Hz samples and emits a raw-input-change notification for axis, button, and touch changes. The browser-side feature `kGamepadRawInputChangeEvent` is enabled by default.

That implementation could provide useful experimental evidence for standardizing an event API while retaining `getGamepads()` for latest-state sampling.


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

Message ID: <w3c/gamepad/issues/4/5941894443@github.com>