https://github.com/w3c/gamepad/pull/163
Enable support for Gamepad API dual-rumble effects through the VibrationManager API added in Android 12.
gamepad, haptics, vibration, rumble, android
Not applicable
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
None
The Chrome team has a limited number of gamepads and Android devices to test with. Implementing this feature behind a flag will enable us to manually test a wider range of devices.
DevTools
Yes, it is already implemented on desktop Blink platforms.
No, this feature cannot be tested using automated tests because it relies on gamepad-specific behavior that can't be mocked.
chrome://flags/#enable-android-gamepad-vibration
False
https://chromestatus.com/feature/5144383549079552
Contact emails
Specification
https://github.com/w3c/gamepad/pull/163
Summary
Enable support for Gamepad API dual-rumble effects through the VibrationManager API added in Android 12.
Blink component
Search tags
gamepad, haptics, vibration, rumble, android
TAG review
Not applicable
Risks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
WebView application risks
None
Goals for experimentation
The Chrome team has a limited number of gamepads and Android devices to test with. Implementing this feature behind a flag will enable us to manually test a wider range of devices.
Debuggability
DevTools
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes, it is already implemented on desktop Blink platforms.
Is this feature fully tested by web-platform-tests?
No, this feature cannot be tested using automated tests because it relies on gamepad-specific behavior that can't be mocked.
Flag name
chrome://flags/#enable-android-gamepad-vibration
Requires code in //chrome?
False
Tracking bug
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5144383549079552
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGhmGSMrh6gjgPW5Z1eWQWzerZs746V6_xNtBfdLrd57ARztmQ%40mail.gmail.com.
Compatibility depends on Android's support which isn't documented. The Android implementation relies on a compatible Linux driver exposing the FF_RUMBLE feature. I've tested a Sony DualShock 4 and a Microsoft Xbox 360 wired controller, both worked. I would expect all of these to work based on the current state of Linux gamepad drivers:
Microsoft Xbox 360 compatible gamepads
Microsoft Xbox One compatible gamepads when connected over USB (but not over Bluetooth)
Official Sony PlayStation 3, 4, 5 gamepads over USB or Bluetooth (but not third party PlayStation compatible gamepads)
Official Nintendo Switch gamepads over USB or Bluetooth (but not third party Switch compatible gamepads)
These devices are handled by the xpad, hid-playstation, hid-sony, and hid-nintendo drivers.
https://github.com/torvalds/linux/blob/master/drivers/input/joystick/xpad.c
https://github.com/torvalds/linux/blob/master/drivers/hid/hid-playstation.c
https://github.com/torvalds/linux/blob/master/drivers/hid/hid-sony.c
https://github.com/torvalds/linux/blob/master/drivers/hid/hid-nintendo.c