Dual-rumble firstTrigger-rumble when availableHonest support checks
Gamepad Vibration Test
Detect whether the browser exposes a vibration actuator, then run quick weak/strong rumble and trigger-rumble checks when supported.
Browsers do not always expose every haptic feature the hardware supports, especially vendor-specific trigger or adaptive feedback.
An unsupported result does not automatically mean the controller is broken. Browser, platform, and connection mode often decide what is exposed.
A new playEffect() call overrides a running effect, which matches the spec behavior.
Support and status
This browser does not support the Gamepad API
Haptics
No
Effect type
--
Last result
--
Samples
0
Select controller
Switch the active pad here when more than one controller is connected.
This browser does not support the Gamepad API
Gamepad API
This browser does not support the Gamepad API
Select controller
--
Haptics
--
Family
--
Vibration controls
Some browsers only support dual-rumble and do not expose trigger-rumble or vendor-specific haptics.
Support and status
The browser or controller does not expose a usable haptics actuator
Haptics
No
Effect type
--
Last result
--
Last error
--
Quick presets
Latest result
Connect a controller, then press any button or move any axis to expose it to the page