Re: [w3c/gamepad] extensions: Add vibrationActuator and dual-rumble effect (PR #163)

@nondebug commented on this pull request.



> +            </li>
+            <li>[=Queue a global task=] on the [=relevant global object=] of
+            |actuator| using the [=gamepad task source=] to run the following
+            steps:
+              <ol>
+                <li>[=Resolve=]
+                |actuator|.{{GamepadHapticActuator/[[playingEffectPromise]]}}
+                with {{GamepadHapticsResult/"preempted"}}.
+                </li>
+                <li>Set
+                |actuator|.{{GamepadHapticActuator/[[playingEffectPromise]]}}
+                to `undefined`.
+                </li>
+              </ol>
+            </li>
+            <li>[=Stop haptic effects=] on |actuator|.

I'm not sure if this is possible. Typically we don't get any feedback from the gamepad when an actuator is started or stopped. The best we can do is confirm that the command was sent to the gamepad.

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

Message ID: <w3c/gamepad/pull/163/review/1103017372@github.com>