- From: Kevin Rajan <notifications@github.com>
- Date: Thu, 01 Oct 2026 15:26:02 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 1 October 2026 22:26:06 UTC
kvnloo left a comment (w3c/gamepad#34) Current Chromium's gamepad provider already treats touch changes as raw-input changes alongside buttons and axes. That suggests touch data should preserve its high-frequency sample/event semantics rather than being exposed only as state observed during `getGamepads()` polling. The new raw-input path could provide implementation experience for this before the touch API is finalized. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/34#issuecomment-5941897568 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/34/5941897568@github.com>
Received on Thursday, 1 October 2026 22:26:06 UTC