Re: [w3c/gamepad] Move vibrationActuator to the main spec (PR #190)

@cabanier commented on this pull request.



> +          Promise<boolean> pulse(double value, double duration);
+        };
+      </pre>
+      <dt>
+        <dfn>pulse()</dfn> method
+      </dt>
+      <dd>
+        <p>
+          <code>pulse()</code> applies a <var>value</var> to the actuator for
+          <var>duration</var> milliseconds. The <var>value</var> passed to
+          <code>pulse()</code> is clamped to limits defined by the actuator
+          type. The returned Promise will resolve <code>true</code> once the
+          pulse has completed.
+        </p>
+        <p>
+          Repeated calls to <code>pulse()</code> override the previous

> Ok, but if pulse() is Meta Quest only, that also puts it the "feature at risk". We should note that in the spec too, unless we expect to get a second implementation.
> Is there a plan for a second implementation?

I'm fairly sure that this was also implemented in the Pico browser. @bkardell , was this added to Wolvic?

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

Message ID: <w3c/gamepad/pull/190/review/1777183286@github.com>