Gamepad Test
Check every button and trigger, watch both analogue sticks, and measure stick drift while the pad sits still. No permission prompt and nothing uploaded, but the browser will not show your controller until you press something on it.
No controller seen yet. Plug it in or connect it, then press any button on the pad.
Browsers deliberately hide gamepads until you do, so an idle controller stays invisible.
What a web page can and cannot see
so you know what these numbers are worth- A press is required first. The Gamepad API returns nothing until the pad sends input, which stops pages using a connected controller as a silent fingerprint.
- Standard mapping is a best effort. Recognised pads report standard and the labels below are correct. Anything else gets raw indices, and button 3 could be anything.
- Rumble is Chromium only. Firefox and Safari expose no vibration actuator, so test 03 will tell you it is unavailable rather than silently doing nothing.
- Drift is measured, not read. Test 02 watches how far the axes wander while you are not touching the sticks. It cannot read a calibration value from the hardware.
Buttons and triggers
Press everything, including both stick clicks and all four D-pad directions. Triggers are analogue on most modern pads, so the number beside LT and RT should sweep rather than jump from 0 to 1.
0Registered
0Reported by pad
Still untested
no controller yet