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

[Bug 21387] New: Need to spec better support for control mapping

From: <bugzilla@jessica.w3.org>
Date: Mon, 25 Mar 2013 12:27:23 +0000
To: public-webapps@w3.org
Message-ID: <bug-21387-2927@http.www.w3.org/Bugs/Public/>

            Bug ID: 21387
           Summary: Need to spec better support for control mapping
    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,

The spec text that talks about a "standard gamepad" layout is a good start, but
I think we need to go a little farther. We should spec a way for
implementations to provide mapping data for known controllers as well as for
content to fill in mappings for devices that the implementation doesn't know

There are two things content will want to know:
1) The mapping of controls to the physical layout of the controller. For
example, most modern gamepads have a left analog stick that's the natural
control for movement, and a set of buttons that are naturally under the right
thumb when holding the controller. Content should be able to locate those to
map them to actions.
2) The naming of controls on the actual gamepad. This is important for
providing feedback to a user, content will want to be able to say "Press A".

Scott has a JS library he wrote that provides this:

I've also started sketching some thoughts in data form of what a useful
presentation of controller data might look like:

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 25 March 2013 12:27:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:59 UTC