W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

[Bug 21386] New: Should specify how to present d-pads/triggers as buttons

From: <bugzilla@jessica.w3.org>
Date: Mon, 25 Mar 2013 12:17:01 +0000
To: public-webapps@w3.org
Message-ID: <bug-21386-2927@http.www.w3.org/Bugs/Public/>
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: ted@mielczarek.org
          Reporter: ted@mielczarek.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org,
                    scott.w3bugzilla@h4ck3r.net

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.
Received on Monday, 25 March 2013 12:17:03 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT