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

@marcoscaceres commented on this pull request.



> +        |params| contains all of the required parameters for |type| effects and
+        all of the parameters have valid values. Additional parameters MUST be
+        ignored.
+      </p>
+      <p>
+        A [=user agent=] that implements this API MUST provide a method to
+        <dfn>issue a haptic effect</dfn> to an actuator with
+        |type:GamepadHapticEffectType| and |params:GamepadEffectParameters|.
+        The [=user agent=] MAY modify the effect to increase compatibility. For
+        example, an effect intended for a rumble motor may be transformed into
+        a waveform-based effect for a device that supports waveform haptics but
+        lacks rumble motors.
+      </p>
+      <p>
+        A [=user agent=] that implements this API MUST provide a method to
+        <dfn>stop haptic effects</dfn> on an actuator. When called, if there is

```suggestion
        <dfn>stop haptic effects</dfn> on an |actuator|. When called, if there is
```

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

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