WebXR Gamepads standardize buttons, triggers, and immersive control axes

The module connects XRInputSource to the Gamepad API and defines the xr-standard mapping. See interoperability, states, and accessibility.

Common mapping reduces specific code

The xr-standard profile gives predictable positions to primary controls when available. The application still needs to query how many buttons and axes each device actually offers.

Living state demands its own comparison

The Gamepad object can be updated in place. To detect pressing, releasing, or crossing a threshold, save a copy of the state before each frame.

Physical control is not universal

Hands, gaze, voice, keyboard and accessibility may be more suitable than a gamepad. Critical functions must have alternative routes and understandable remapping.

Capabilities can identify devices

Combinations of buttons and axes contribute to fingerprinting. Collect only what is necessary and avoid detailed telemetry without purpose and consent.

Nexus Reading

Interoperability is born from semantic actions, not button numbers. Model pick up, confirm and return; then associate these actions with the capabilities detected in each control.

FAQ

Does xr-standard make all controls the same?

No. It normalizes part of the mapping, but devices still have different capabilities and formats.

How to detect a new click?

Compare the current state with a copy of the previous frame, because the exposed object can be continually updated.

Do I need to offer another input?

It is recommended, especially for accessibility and devices without the expected set of buttons or axes.

Essential guides to delve deeper into the decision