This is an experimental technology
Because this technology's specification has not stabilized, check the compatibility table for the proper prefixes to use in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the spec changes.
The Gamepad API is a way for developers to access and respond to signals from gamepads and other game controllers in a simple, consistent way. It contains three interfaces, two events and one specialist function, to respond to gamepads being connected and disconnected, and to access other information about the gamepads themselves, and what buttons and other controls are currently being pressed.
The following interfaces are defined in the Gamepad API
The Gamepad API also defines some events and a specialist function:
Specialist events on the
Windowobject that allows us to react when a gamepad is connected or disconnected:
gamepaddisconnected. Event handlers can be easily set using
An extension to the
Navigatorobject that returns an array of
Gamepadobjects, one for each connected gamepad.
Tutorials and guides
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari (WebKit)|
|General support||21.0 webkit||24.0 (24.0) moz
|Not supported||Not supported||Not supported|
|Feature||Android||Firefox Mobile (Gecko)||IE Phone||Opera Mobile||Safari Mobile|
|General support||Not supported||Not supported||Not supported||Not supported||Not supported|
- Editor's Draft at the W3C
- The Gamepad API by Ted Mielczarek and Robert Nyman
- Simple API demo page - https://bug604039.bugzilla.mozilla.org/attachment.cgi?id=549214
- Another API demo page - https://bug604039.bugzilla.mozilla.org/attachment.cgi?id=550638
- Example of using MozGamepad* listeners - https://gist.github.com/58b0f9ed647f72da9173