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

FWIW, given the "The same object MUST be returned until the user agent needs to return different values (or values in a different order)" wording for [`axes`](https://w3c.github.io/gamepad/#dom-gamepad-axes) and `buttons`, it seems like it was at one point the intention for a `Gamepad` object to be live in the sense that its attributes can start returning new values, and this does make sense to me. `Gamepad` objects do have an `id`, but to have to call `navigator.getGamepads()` for every animation frame seems odd given the naming of the API.

-- 
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-541765600