Why are there strong and weak controls?
The standard API names low-frequency strength and high-frequency weakness separately.
Feature detection shows only effects exposed by this controller/browser pair. Strong means low-frequency and weak means high-frequency—not left and right motors.
Keep the page visible and focused.
A complete result means the browser accepted the requested effect. Unsupported or preempted is a compatibility result, not proof of broken hardware.
The standard API names low-frequency strength and high-frequency weakness separately.
It appears only when the browser explicitly exposes trigger-rumble.