Re: [w3c/gamepad] Spec liveness of Gamepad and GamepadButton objects (#8) (#123)

nondebug commented on this pull request.



> @@ -318,7 +323,13 @@ <h2>
       </h2>
       <p>
         This interface defines the state of an individual button on a gamepad
-        device.
+        device. A GamepadButton is a live object; that is, user interaction with
+        the button represented by the object will be reflected in the object's
+        properties. When the system receives new data from a connected gamepad,
+        a microtask is queued in the current event loop to update the state of
+        the GamepadButton object. If a gamepad device is disconnected, the

Good idea. I uploaded a new commit where I've pulled out behavior that should be tied to system events (gamepad connection, gamepad disconnection, gamepad state update). Eventually these should be combined into an algorithm for each system event.

-- 
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/pull/123#discussion_r343920723