我们的志愿者还没有将这篇文章翻译为 中文 (简体)。加入我们帮助完成翻译！
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 The definition of 'GamepadEvent' in that specification. |
Working Draft | Initial definition |
Browser compatibility
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari (WebKit) |
|---|---|---|---|---|---|
| General support |
21.0 webkit |
29.0 (29.0) | Not supported |
15.0 webkit |
Not supported |
| Feature | Android | Firefox Mobile (Gecko) | IE Phone | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|
| General support | Not supported | 32.0 (32.0) | Not supported | Not supported | Not supported |