Bug 21386 - Should specify how to present d-pads/triggers as buttons
Should specify how to present d-pads/triggers as buttons
Status: NEW
Product: WebAppsWG
Classification: Unclassified
Component: Gamepad
All All
: P2 normal
: ---
Assigned To: Ted Mielczarek [:ted]
Depends on:
  Show dependency treegraph
Reported: 2013-03-25 12:17 UTC by Ted Mielczarek [:ted]
Modified: 2014-12-17 22:14 UTC (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Ted Mielczarek [:ted] 2013-03-25 12:17:01 UTC
Currently the spec requires implementations to express the set of controls on a controller in two arrays: buttons and axes. All of the platform APIs I've used expose a set of buttons and a set of axes, so this makes sense. However, there are also frequently some controls that aren't exposed as either of those, so some internal mapping is required. For example, d-pads are frequently exposed as a "POV hat" (since the USB HID was written in the days of actual flight-stick like joysticks).

I think we need to have some spec text that speaks to how to put these controls into the list of buttons/axes so that the list of controls are consistent across browsers (at least for the same OS+driver combination).