https://www.w3.org/Bugs/Public/show_bug.cgi?id=21386
Bug ID: 21386
Summary: Should specify how to present d-pads/triggers as
buttons
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Gamepad
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected],
[email protected]
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).
--
You are receiving this mail because:
You are on the CC list for the bug.