Re: [w3c/gamepad] Gamepad event timing (#83)

I'm pursuing this in support of adding gamepad button and axis events, which should require stricter timing so that listeners receive button and axis events in a predictable order. These events should also be dispatched correctly with respect to connection events to ensure we don't dispatch button and axis events for a gamepad that hasn't dispatched gamepadconnected yet.

I've also run into issues with test APIs that are capable of changing gamepad state from inside an event listener. This may cause re-entry into the event handler (e.g., by changing a gamepad to disconnected while inside the gamepadconnected listener) which can lead to unexpected behavior. Perhaps the gamepad API should specify more broadly when gamepad state may or may not be changed in order to better support test APIs like this.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/83#issuecomment-413636028