Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)

Here's a specific minimal proposal to try to unblock the [chromium issue](https://codereview.chromium.org/1680143002/):

- Add `DOM_KEY_LOCATION_GAMEPAD` that indicates the key event comes from a device that's also exposed by the [W3C Gamepad API](https://w3c.github.io/gamepad/)
- Add (at least) `Button0` to the [code spec](https://w3c.github.io/uievents-code/), defined to be equivalent to `buttons[0]` in [the standard Gamepad API mapping](https://w3c.github.io/gamepad/#remapping)
- Add (at least) `ButtonA` to the [key spec](https://w3c.github.io/uievents-key/).  
  - Alternately perhaps it's not unreasonable to re-use "Execute" or "Navigate" when chromium wants to map BUTTON_A to a general execution action?

---
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/uievents/issues/79#issuecomment-227562123