The GamepadEvent Interface of the Gamepad API contains references to gamepads connected to the system, which is what the gamepad events Window.gamepadconnected and Window.gamepaddisconnected are fired in response to.
Note: These events are not fired in Chrome, only Firefox. In Chrome you have to use Navigator.getGamepads() to access Gamepad objects.
Properties
-
GamepadEvent.gamepadRead only -
Returns a
Gamepadobject, providing access to the associated gamepad data for the event fired.
Examples
The gamepad property being called on a fired Window.gamepadconnected event.
window.addEventListener("gamepadconnected", function(e) {
console.log("Gamepad connected at index %d: %s. %d buttons, %d axes.",
e.gamepad.index, e.gamepad.id,
e.gamepad.buttons.length, e.gamepad.axes.length);
});
And on a Window.gamepaddisconnected event.
window.addEventListener("gamepaddisconnected", function(e) {
console.log("Gamepad disconnected from index %d: %s",
e.gamepad.index, e.gamepad.id);
});
Specifications
| Specification | Status | Comment |
|---|---|---|
| Gamepad | Working Draft |
Browser compatibility
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari (WebKit) |
|---|---|---|---|---|---|
| General support | 21.0 webkit | 24.0 (24.0) moz 28.0 (28.0) |
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 |
See also
Document Tags and Contributors
Tags:
Contributors to this page: chrisdavidmills
Last updated by:
chrisdavidmills,