- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Wed, 15 May 2024 01:36:14 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 15 May 2024 08:36:18 UTC
So three use cases: 1. Show matching icon for each controller 2. Feature detection for buttons 3. Identify each controller 1 may be fun but not sure it's important enough. 2 should be solved by #196. 3 sounds like a workaround rather than actual direct use case of this, how can I identify each controller by name if I have 4 Xbox 360 controllers connected? Should the application instead vibrate each controller for example so that I can know which is which? It's not adding a new fingerprinting vector, but this still eases use of unnecessarily exposed device specific info that I'd rather discuss removing `id` to resist fingerprinting and add missing features that this might solve as #196 does. (i.e. I think two feature-equivalent gamepads should be perceived equivalent to Gamepad API even if those are different products. Like how we don't allow differentiating a Logitech mouse and Microsoft mouse.) -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/pull/202#issuecomment-2111903174 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/pull/202/c2111903174@github.com>
Received on Wednesday, 15 May 2024 08:36:18 UTC