Browser Controller Tests: Capabilities and Limits

Guide: Browser Controller Tests: Capabilities and Limits Check the method, connection and limits of browser inputs.

What the API exposes

The Gamepad API provides buttons, axes and device information exposed by the browser. That is a useful view of received inputs, but it is not direct access to every physical sensor. Mappings and available features differ between controller, connection, operating system and browser.

Observed values are not physical timing

A page typically reads snapshots during animation frames. The number of observed changes is not automatically the controller’s USB polling rate. Measuring physical action-to-display latency needs a suitable method beyond these plots.

Keep sample data separate

Demo mode illustrates the interface without a device. Its readings cannot support a judgment about your own controller. Downloaded demo reports carry an explicit simulated-data label; real reports describe only browser-observed data.

Test the claim, not the appearance

A neat gauge does not establish accuracy. Check which inputs a tool uses, how long it samples and what happens when the device disconnects. InputHarbor exposes numbered raw inputs and documents its rest-measurement formula.

Updated 2026-11-17