GamepadEvent
Baseline
Widely available
*
This feature is well established and works across many devices and browser versions. It’s been available across browsers since March 2017.
* Some parts of this feature may have varying levels of support.
The GamepadEvent interface of the Gamepad API contains references to gamepads connected to the system, which is what the gamepad events gamepadconnected and gamepaddisconnected are fired in response to.
Constructor
GamepadEvent()-
Returns a new
GamepadEventobject.
Instance 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 gamepadconnected event.
js
window.addEventListener("gamepadconnected", (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 gamepaddisconnected event.
js
window.addEventListener("gamepaddisconnected", (e) => {
console.log(
"Gamepad disconnected from index %d: %s",
e.gamepad.index,
e.gamepad.id,
);
});
Specifications
| Specification |
|---|
| Gamepad # gamepadevent-interface |
Browser compatibility
| desktop | mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
GamepadEvent
|
|
|
|
|
|
|
|
|
|
|
|
|
GamepadEvent() constructor
|
|
|
|
|
|
|
|
|
|
|
|
|
gamepad
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Secure context required
|
|
|
|
|
|
|
|
|
|
|
|
|
Legend
Tip: you can click/tap on a cell for more information.
- Full support
- Full support
- No support
- No support
- Experimental. Expect behavior to change in the future.
- User must explicitly enable this feature.