Re: [w3c/gamepad] Vibrate feature for Gamepad (#19)

As with most things, I think we're still primarily blocked on figuring out a sensible API that can expose the features of modern devices without being painful to use. We wanted to try to reuse the Web Vibration API interfaces, but they are not expressive enough for the needs of the Gamepad API. Primarily:
* Multiple vibration motors per device: most modern gamepads have two, the Xbox One controller has four, and generally the motors are of varying strengths. (Usually at least one strong and one weak vibration motor.)
* Vibration motors allow setting the vibration strength, not just the duration.

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