Chrome Version: 65.0.3325.124 (Official Build) beta (64-bit)
OS: OS X 10.13.2

What steps will reproduce the problem?
1. Connect an Xbox One gamepad via microUSB cable
2. Navigate to html5gamepad.com and press a button on the gamepad so it shows up in the list.
3. Open the Developer Tools console and run this command:

pad.vibrationActuator.playEffect('dual-rumble', { duration: 5000, weakMagnitude: 1.0 }).then(r => {console.log(r)})

What is the expected result?

Gamepad vibrates for 5 seconds, then stops vibrating just as "complete" is printed to the console.

What happens instead?

Gamepad vibrates for ~3 seconds, then stops vibrating. ~2 seconds later, "complete" is printed to the console.




The Xbox One rumble packet specifies effect duration as an 8-bit unsigned value. Chrome always sets this to the maximum value (0xff) and issues a second rumble packet with 0 intensity when vibration should be stopped. However, this fails when the effect duration is longer than the maximum supported by the rumble packet.

To fix this, Chrome should identify when a vibration effect is longer than the maximum duration supported by the packet and issue a new packet to continue the effect.
 

Chrome Version: 65.0.3325.124 (Official Build) beta (64-bit)
OS: OS X 10.13.2

What steps will reproduce the problem?
1. Connect an Xbox One gamepad via microUSB cable
2. Navigate to html5gamepad.com and press a button on the gamepad so it shows up in the list.
3. Open the Developer Tools console and run this command:

var pads = navigator.getGamepads();
pads[0].vibrationActuator.playEffect('dual-rumble', { duration: 5000, weakMagnitude: 1.0 }).then(r => {console.log(r)})

What is the expected result?

Gamepad vibrates for 5 seconds, then stops vibrating just as "complete" is printed to the console.

What happens instead?

Gamepad vibrates for ~3 seconds, then stops vibrating. ~2 seconds later, "complete" is printed to the console.




The Xbox One rumble packet specifies effect duration as an 8-bit unsigned value. Chrome always sets this to the maximum value (0xff) and issues a second rumble packet with 0 intensity when vibration should be stopped. However, this fails when the effect duration is longer than the maximum supported by the rumble packet.

To fix this, Chrome should identify when a vibration effect is longer than the maximum duration supported by the packet and issue a new packet to continue the effect.