Re: [w3c/gamepad] Add a means to test the API (Issue #175)

kvnloo left a comment (w3c/gamepad#175)

One addition seems increasingly useful: timestamped input injection.

Chromium now polls gamepads at ~250 Hz and has a `GamepadRawInputChanged` path. If the automation API can inject an axis/button transition with a known timestamp, tests can verify:

- state propagation,
- event ordering,
- snapshot/event consistency,
- latency from injected sample to observable state/event.

That would turn several long-standing timing questions into reproducible tests.


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

Message ID: <w3c/gamepad/issues/175/5941896811@github.com>