[uievents] Should key codes / location exist for gamepads? (#79)

This started as a [blink implementation discussion](https://codereview.chromium.org/1680143002/), but I think the important question here is really a platform API decision.

If a (otherwise normal) web-page wants to optimize it's behavior when being navigated by a gamepad, is the [Gamepad API](https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API/Using_the_Gamepad_API) always the best choice?  Eg. when the Gamepad API is in use, gamepad browser navigation features (like built-in scrolling controls) must be disabled, and it's probably not easy / practical for the web developer to re-implement scrolling support (matching the browser default conventions) on top of the low-level Gamepad API.  Also it's weird for a normal document-style page to need a "game loop" to detect (probably rare) button presses, rather than just having events the way a keyboard does.

So maybe it's also reasonable (as @garykac [suggests](https://codereview.chromium.org/1680143002/#msg29)) to generate Keyboard events for gamepad buttons?

@sgraham @garykac Thoughts?

---
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