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

@gabrielsanbrito commented on this pull request.



> @@ -153,6 +153,7 @@ <h2>
           readonly attribute GamepadMappingType mapping;
           readonly attribute FrozenArray&lt;double&gt; axes;
           readonly attribute FrozenArray&lt;GamepadButton&gt; buttons;
+          [SameObject] readonly attribute GamepadHapticActuator? vibrationActuator;

I don't know. It makes sense to me at least. I have used a few gamepad devices in the past that didn't have any sort of vibration actuators. It makes sense to me to have it being `null` instead of having an empty `GamepadHapticActuator.effects` array. What do you think?

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

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