Browser limits
What a browser can and cannot read from a controller, and why results can differ between browsers.
Press a button first
Browsers show a controller to a page only after you press one of its buttons while the page is open. This keeps websites from seeing your devices without you knowing.
What every browser can read
Buttons, triggers and sticks, through the standard gamepad interface. When a browser does not recognise the controller's layout, PadProof shows numbered buttons and axes instead of named ones, and some tests may be limited.
Update rate
A browser can report the controller less often than the controller sends data, and it slows pages down in background tabs. Keep PadProof visible while a test runs. If the update rate test gives a low result, try another browser or a cable before you blame the controller.
The home button
Some systems keep the home button for themselves, so the browser never sees it. PadProof marks it as not testable here instead of failing it.
What needs more than a browser
Battery level, touchpad, motion sensors and stick calibration need direct access to the controller. Only Chrome and Edge on a computer offer it, and PadProof will use it in its next phase.