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

> (But it's also fine to construct a new array for each call.)

That's not great, either store the JavaScript array object on the object and replace it when needed, or always create a new array based on the internal data.

> should return

Must, right? (Same for other shoulds.)

> other members may be updated due to user interaction with the gamepad

This will have to be defined as updating internal state on the `Gamepad` objects at a specific point in time to avoid violating run-to-completion semantics. (You're saying as much at the end, but I hope the eventual definition of this will fall out of the processing model.)

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