[w3c/gamepad] DOM Elements Integration (Issue #227)

DanielHerr created an issue (w3c/gamepad#227)

We have always had keyboard and mouse integration with DOM elements, but not with game controllers. It makes sense to use something like a device specific input API like the current gamepad API when you are connecting input to a game engine, but not so much when you are just trying to provide input for a DOM UI. Most applications made for a game console or smart TV have a concept of focus similar to DOM keyboard focus but which can be moved around in multiple directions and a primary button press which works like a mouse click. It would be nice if the DOM had proper integration with game controller input, both providing input events to the currently focused element, and working in browser UI where keyboard/mouse input does, such as select or video elements.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/227
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/227@github.com>