[w3c/gamepad] Shouldn't Gamepad.vibrationActuator be nullable? (Issue #178)

It is currently not marked as nullable in the Web DIL here:
- https://w3c.github.io/gamepad/extensions.html#partial-gamepad-interface

However, the specification for "Construction" seems to indicate it can be null:
> Add new steps to a new Gamepad:

> If gamepad has a vibration actuator that can [play effects with type](https://w3c.github.io/gamepad/extensions.html#dfn-play-effects-with-type) "[dual-rumble](https://w3c.github.io/gamepad/extensions.html#dom-gamepadhapticeffecttype-dual-rumble)", initialize gamepad's [vibrationActuator](https://w3c.github.io/gamepad/extensions.html#dom-gamepad-vibrationactuator) attribute to [a new GamepadHapticActuator](https://w3c.github.io/gamepad/extensions.html#dfn-a-new-gamepadhapticactuator) with "[dual-rumble](https://w3c.github.io/gamepad/extensions.html#dom-gamepadhapticactuatortype-dual-rumble)".
Otherwise, initialize gamepad's [vibrationActuator](https://w3c.github.io/gamepad/extensions.html#dom-gamepad-vibrationactuator) attribute to null.

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

Message ID: <w3c/gamepad/issues/178@github.com>