Re: [w3c/gamepad] Spec gamepad input events (PR #234)

@gabrielsanbrito commented on this pull request.



> @@ -870,7 +892,7 @@ <h3>
               <li>Let |normalizedValue:double| be 2 (|logicalValue| −
               |logicalMinimum|) / (|logicalMaximum| − |logicalMinimum|) − 1.

Filed #238.

> @@ -825,20 +833,34 @@ <h3>
                       <li>Set |connectedGamepad|.{{Gamepad/[[timestamp]]}} to
                       |now|.
                       </li>
-                      <li>If |document| is not `null` and is [=Document/fully
-                      active=], then [=queue a global task=] on the [=gamepad
-                      task source=] to [=fire an event=] named
-                      {{gamepadconnected}} at |gamepad|'s [=relevant global
-                      object=] using {{GamepadEvent}} with its
-                      {{GamepadEvent/gamepad}} attribute initialized to
-                      |connectedGamepad|.
+                      <li>[=Fire an event=] named {{gamepadconnected}} at

This was modified while addressing this comment: https://github.com/w3c/gamepad/pull/234#discussion_r4099569185

I believe that the rationale is that, since the [update gamepad state](https://w3c.github.io/gamepad/#dfn-update-gamepad-state) already run in a task posted on the gamepad task source, we can just fire the event directly without posting another task.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/234#discussion_r4396054774
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/pull/234/review/5676723582@github.com>