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

nondebug commented on this pull request.



> @@ -209,7 +209,11 @@ <h2>
         <dfn>Gamepad</dfn> interface
       </h2>
       <p>
-        This interface defines an individual gamepad device.
+        This interface represents an individual gamepad device. A Gamepad is a
+        live object; that is, user interaction with the device will be reflected
+        in the state of the object's properties. When the system receives new
+        data from a connected gamepad, a microtask is queued in the current

That seems like the best approach. According to the HTML5 spec, input events should be queued this way:

"Asynchronous events sent in response to user input (e.g. click events) must be fired using tasks queued with the user interaction task source."

https://www.w3.org/TR/2014/REC-html5-20141028/webappapis.html#generic-task-sources

I think specifying the live object updates in terms of the user interaction task source will make it easier to spec gamepad button/axis events in the future.

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