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

To clarify, I'm no longer an editor on this spec.

Speaking from the perspective of an editor within the Immersive Web Working Group, however, I understand the concern that our use of gamepad differs from how this spec text implies they should be used. It is worth noting that every Gamepad implementation I'm familiar with does update the gamepad objects in-place upon calling getGamepads(), which seems to contradict the spec text. I'm skeptical that the UA implementations will change to match the spec text any time soon, given that I believe it's already been previously identified by Microsoft as a content compatibility issue. As such, I would rather that WebXR be consistent with the observed behavior of gamepads rather than the single sentence in the Gamepad spec that states they should behave otherwise.

That said, I also don't think the spec and implementations should disagree. It would be best if either the spec updated to reflect the currently observed behavior accurately or we get agreement from all UAs that they will update `getGamepads()` to return actual snapshots. If this group takes the latter route then WebXR would be willing to change to match, especially given that backwards compatibility will already be broken at that point. In the meantime, since it's not clear which direction the Gamepad group wants to go, WebXR will continue with (and ship) a live attribute.

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