- From: Steve Agoston <notifications@github.com>
- Date: Mon, 05 Aug 2019 10:34:58 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 5 August 2019 17:35:20 UTC
While Gamepad#id is not ideal, especially with the same controller getting a different id reported on different browsers, there is a use case we must support. When a game needs to display a help screen which shows which button/axis performs which game action, the game UI replies on know what type of controller is being used. Here's an example: https://www.reddit.com/r/SteamController/comments/693sb6/prey_2017_has_native_steam_controller_api_support/ I agree that feature detection should be used but we cannot simply drop this field. I don't know if we can always rely on vendor/product ids being available with some of the underlying native APIs. Any proposals for how we can at least make the id field consistent across browser implementations? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/73#issuecomment-518327517
Received on Monday, 5 August 2019 17:35:20 UTC