Properly set initial button/axis state for new gamepads

NEW
Unassigned

Status

()

Core
DOM: Events
5 years ago
4 years ago

People

(Reporter: ted, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
The current Gamepad API patch simply initializes new Gamepads with zeroed-out .buttons and .axes arrays. It should instead ensure that it has the current states of each control so that we don't generate spurious events when we get the first set of data.
(Reporter)

Updated

4 years ago
Blocks: 1084610
You need to log in before you can comment on or make changes to this bug.