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

> @gabrielsanbrito, I merged in my suggestions and rebased.
> 
> The last remaining thing is just adding the DOMHighResTimestamp suggestion. Do you want me to do that?

Thanks for doing that, @marcoscaceres! I was looking up on how to do the DOMHighResTimestamp. I was thinking on something like this:
```
<li>Let {{GamepadHapticActuator/[[playingEffectPromise]]}} be [=a
new promise=].
<li>Let |playEffectTimestamp:DOMHighResTimestamp| be the [=current high resolution time=] given the |document|'s [=relevant global object=].
</li>
<li>Do the following steps [=in parallel=]:
  <ol>
    <li>[=Issue a haptic effect=] to the actuator with |type|, |params|, and the 
     |playEffectTimestamp|.
    </li>
[...]
```

Then, on the <dfn>issue a haptic effect</dfn>, I was thinking of adding:
```
To <dfn>issue a haptic effect</dfn> on an actuator, the [=user agent=] MUST send a command to the device to render an effect of |type:GamepadHapticEffectType| and try to make it use the provided |params:GamepadEffectParameters|. The [=user agent=] SHOULD use the provided |playEffectTimestamp:DOMHighResTimestamp| for more precise playback timing when |params|.{{startDelay}} is not `0.0`.
```

What do you think? Please feel free to add it directly if it is too far from ideal.

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

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