English
Gamepad and Controller Stick Drift Test
Inspect live browser button, trigger, and axis values; exercise every control; and measure neutral-stick drift against a disclosed practical threshold.
Controller input bench
Browsers normally hide gamepads until a deliberate controller gesture is detected. Wired, Bluetooth, Xbox, PlayStation, and many standard USB controllers are supported when the browser exposes them.
Waiting for a controller gesture
Press a controller button so the browser can expose the device without weakening fingerprinting protections.
Button, trigger, and axis values come from the browser Gamepad API. Controller firmware, operating-system drivers, browser mapping, Bluetooth quality, and game-specific dead zones may produce different results. Haptic support is optional and an unavailable vibration command is not a controller failure.
Separate browser mapping from controller hardware.
A game can apply its own remapping, dead zone, response curve, and vibration support after the browser reports these raw values.
Press a controller button, reconnect it, and retry in a current Chromium or Firefox browser.
Repeat neutral calibration on a stable surface, then compare the game’s own dead-zone setting.
Do not treat this alone as hardware failure; verify haptics in a supported game or native controller utility.
Gamepad controls
How this test works
Buttons and axes are values exposed by the Gamepad API. The neutral-stick check uses ±0.12 as a practical screening band, not a manufacturer tolerance.
What this cannot establish
Mappings, dead zones, and optional vibration differ by browser, driver, and game. Test untouched sticks repeatedly and compare in a game or the manufacturer's utility before calling a controller defective.
Recheck before replacing hardware
Change one variable at a time, repeat under the same conditions, and compare with the operating system or the affected application. An unavailable reading is not a pass.