NOTE: This document is no longer maintained because the Web Applications Working Group was closed in October 2015 and its deliverables transferred to the Web Platform Working Group. The information in this document was copied to https://github.com/w3c/gamepad/blob/gh-pages/FeatureRequests.md.
This document includes feature requests and new requirements for the next version of the Gamepad specification; that is features that are not included in the first version of the spec.
Those with write access to this document are encouraged to update this document and/or to use Bugzilla to submit a feature request. If you cannot create a Bugzilla bug to request a new feature or requirement, please send your request to WebApps' firstname.lastname@example.org list with a Subject header of
Feature for Next Version
- Most modern gamepads contain vibration motors
- Discussed several times on public-webapps
- Related work, WebVibration, spec editor is open to the idea of working together
- Some prototype work in Mozilla's bugzilla
- Supported in some modern controllers (DualShock 3/4?, Wii remote)
- Better mapping support
- Event-based update mechanism
- Discussed on public-webapps: http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0469.html
- Firefox contains a prototype implementation of ButtonEvent/AxisMoveEvent behind a pref (dom.gamepad.non_standard_events.enabled)
- Capture/lock feature
- Similar to mouse lock / pointer lock API - ability to capture gamepad inputs before they're mapped to (emulated) mouse/keyboard controls by user agent
- Mentioned on public-webapps, with use case already for Mozilla/Ouya