Re: [w3c/gamepad] Need to spec liveness of Gamepad objects (#8)

If both Firefox and Chrome's implementations do not match the spec text then I think the spec text should be changed to match the implementations. Someone should test Safari and Edge as well. I was under the impression that the Chrome implementation was snapshots, but perhaps that changed over time?

Regardless, last I knew the Firefox implementation actually implemented updates to Gamepad objects by doing the internal equivalent of queuing microtasks to update the state, so using some spec language like "Updates to Gamepad objects should be queued as microtasks in the current event loop" should both be sensible and not contradict the Firefox implementation. Note that there have been requests to [add support for the Gamepad API to Web Workers](https://github.com/w3c/gamepad/issues/37) so ideally the spec text could be written to not make it more difficult to add that in the future.

[There are some existing manual web platform tests](https://github.com/web-platform-tests/wpt/tree/master/gamepad), it should be possible to write new tests for this behavior.

-- 
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/8#issuecomment-543183532