- From: Matt Reynolds <notifications@github.com>
- Date: Thu, 28 May 2020 16:59:02 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 May 2020 23:59:14 UTC
> The Gamepad API should be based on this API, particularly since many of the stated use cases are around Gamepads. e.g. could the Gamepad API be implemented as a polyfill using this API? Only a subset of gamepads are HID. Additionally, I believe it's better for browsers to consume gamepad input through the platform's gamepad-specific input API. HID should be used as a last resort for gamepads that aren't exposed through higher level APIs. That said, I do think there's an opportunity for WebHID-based polyfills that provide support for novel HID gamepads. Note that a WebHID-based polyfill would require a chooser dialog that isn't needed for normal Gamepad access. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/370#issuecomment-635678695
Received on Thursday, 28 May 2020 23:59:14 UTC