HOW THE TESTER WORKS
Measurements with context.
Every report describes what this browser observed. It is not a hardware certification.
Input source and sampling
The tester reads the browser’s Gamepad API while the tab is visible. It displays snapshots of exposed buttons and axes. Rendering and browser scheduling can miss brief changes; the update cadence is not advertised as a controller’s hardware polling rate.
Standard and non-standard mappings
Named diagnostics use a standard mapping with at least four axes and sixteen buttons. Axes 0/1 and 2/3 are treated as the left and right sticks; buttons 6 and 7 are used for the trigger values. Otherwise the tester shows raw indices instead of guessing the layout.
Resting-stick offset
For each sample, radial offset is √(X² + Y²). The report includes the sample count, mean radius, nearest-rank 95th percentile, maximum radius and mean X/Y. Percentages multiply the normalized radius by 100. Diagonal input can exceed 100% because each axis has its own range.
The resting test runs for ten seconds. Changing controllers, resetting the session or hiding the tab stops an unfinished measurement. No universal pass/fail threshold is assigned.
Range coverage
The range tracker divides stick direction into sixteen sectors and stores the maximum radius observed in each. A sector is counted as visited at radius 0.75 or greater. The exported outline-deviation value, available after all sectors are covered, is the mean absolute difference between those maxima and radius 1. It is a geometric description, not an accuracy score.
Buttons, triggers and rumble
A button is marked observed when its pressed flag is true or its exposed value exceeds 0.5. Trigger maximums are the largest exposed values sampled during the session. A vibration completion message reflects the browser’s result; the user must confirm the physical sensation.
Reports and reproducibility
Reports include the browser-reported device name, mapping, input counts, browser user agent, time, optional setup note and observed results. Demo reports are explicitly marked. Compare one change at a time and keep connection, firmware, software profile and browser consistent.