IMPORTANT:
- This launch issue is used for standards and implementation tracking only.
It is NOT for Chrome approval regarding privacy, security, legal, UI,
testing,
accessibility etc.
- An overview of the different launch issues can be found here:
http://bit.ly/2ncKZfp
- If your feature requires security / privacy / etc approval then seek a PM
to guide you through the go/newchromefeature process

See http://www.chromium.org/blink#launch-process for an overview of the
Blink launch process, but note this doesn't cover security / privacy / etc
reviews as discussed above.

----------

Change description:

Extend the Gamepad API to support dual-rumble style haptic effects.

Changes to API surface:

* The Gamepad interface will be extended to include a vibrationActuator attribute with type GamepadHapticActuator.
* A GamepadHapticActuator interface will be added to represent haptic feedback components. It will expose a createEffect method that takes an effect description and returns a GamepadHapticEffect object representing a handle to the effect.
* A GamepadHapticEffect interface will be added as a handle for haptic effects. It will expose a play method to initiate playback of the effect.

Links:
Public standards discussion:

Discussion on public-webapps from 2014
https://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0722.html

Gamepad Vibration github issue
https://github.com/w3c/gamepad/issues/19#issuecomment-306959243

Chromium issue
 http://crbug.com/749295 

Support in other browsers:
Internet Explorer: Not supported
Firefox: Stalled (https://bugzilla.mozilla.org/show_bug.cgi?id=680289)
Safari: Not supported