Treat a completed multi-sample window as evidence of the browser-delivered controller signal.
IP-CTL-01 / AXES / BUTTONS / TIME
Controller Button Test
Verify press and release transitions, analog button values and possible stuck inputs.
A face, shoulder, menu or D-pad button is missed or remains active.
This focused entry uses the shared Controller protocol. The measurement logic and Evidence version remain identical to the complete lab.
Remove the easiest false alarms first.
01
Connect one controller, press a button and keep this tab visible.
02
Place the controller on a stable surface before any idle capture.
03
Test USB and Bluetooth as separate sessions instead of changing mid-run.
Run one repeatable protocol.
- 01
Activate the controller in the browser.
- 02
Press and release each button once.
- 03
Inspect the bounded transition timeline for missing releases or repeats.
Evidence the result should expose.
DIRECT / INFERREDButton value
DIRECT / INFERREDPress/release state
DIRECT / INFERREDTransition time
DIRECT / INFERREDInput timeline
Separate observed, review and inconclusive.
Repeat the same protocol twice with the same connection before escalating persistent drift, bounce or missed transitions.
No Gamepad API signal, an unsupported actuator or one release spike cannot prove a physical controller fault.
Start with the likely path, then retest.
01
Worn switch
02
Controller mapping
03
Application input capture