Abstract

The Gamepad specification defines a low-level interface that represents gamepad devices.

Status of This Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C standards and drafts index.

This is a work in progress.

This document was published by the Web Applications Working Group as a Working Draft using the Recommendation track.

Publication as a Working Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to cite this document as other than a work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent that the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 03 November 2023 W3C Process Document.

This section is non-normative.

Some user agents have connected gamepad devices. These devices are desirable and suited to input for gaming applications, and for "10 foot" user interfaces (presentations, media viewers).

Currently, the only way for a gamepad to be used as input would be to emulate mouse or keyboard events, however this would lose information and require additional software outside of the user agent to accomplish emulation.

Meanwhile, native applications are capable of accessing these devices via system APIs.

The Gamepad API provides a solution to this problem by specifying interfaces that allow web applications to directly act on gamepad data.

Interfacing with external devices designed to control games has the potential to become large and intractable if approached in full generality. In this specification we explicitly choose to narrow scope to provide a useful subset of functionality that can be widely implemented and broadly useful.

Specifically, we choose to only support the functionality required to support gamepads. Support for gamepads requires two input types: buttons and axes. Both buttons and axes are reported as analog values, buttons ranging from [0 .. 1], and axes ranging from [-1 .. 1].

While the primary goal is support for gamepad devices, supporting these two types of analog inputs allows support for other similar devices common to current gaming systems including joysticks, driving wheels, pedals, and accelerometers. As such, the name "gamepad" is exemplary rather than trying to be a generic name for the entire set of devices addressed by this specification.

We specifically exclude support for more complex devices that may also be used in some gaming contexts, including those that that do motion sensing, depth sensing, video analysis, gesture recognition, and so on.

A gamepad is a collection of input controls and output controls. An input control has a collection of input values that may update over time. Input controls include the buttons, triggers, joysticks, thumbsticks, and touch surfaces of the gamepad. An output control is a feature that changes the behavior of the gamepad to provide feedback to the user interacting with the gamepad. Output controls include the haptic actuators of the gamepad. A gamepad is available if the user agent can read the current state of its input controls. A gamepad that is not available is unavailable . The input controls and output controls for a gamepad cannot change while the gamepad is available.

The user agent is responsible for:

• Enumerating available gamepads,
• Detecting when gamepads become available or unavailable,
• Detecting when input controls have updated input values,
• Reading the current state of input values, and
• Commanding the gamepad to use its output controls.

A gamepad has a gamepad identifier string , a human-readable string that identifies the brand or style of gamepad. The content is decided by the user agent.

This interface defines an individual gamepad device.

[Exposed=Window]
interface Gamepad {
  readonly attribute DOMString id;
  readonly attribute long index;
  readonly attribute boolean connected;
  readonly attribute DOMHighResTimeStamp timestamp;
  readonly attribute GamepadMappingType mapping;
  readonly attribute FrozenArray<double> axes;
  readonly attribute FrozenArray<GamepadButton> buttons;
  readonly attribute FrozenArray<GamepadTouch> touches;
  [SameObject] readonly attribute GamepadHapticActuator vibrationActuator;
};

The algorithms used to communicate with the system typically complete asynchronously, queuing work on the gamepad task source .

Instances of Gamepad are created with the internal slots described in the following table:

id attribute

An identification string for the gamepad. This string identifies the brand or style of connected gamepad device.

The exact format of the id string is left unspecified. It is RECOMMENDED that the user agent select a string that identifies the product without uniquely identifying the device. For example, a USB gamepad may be identified by its idVendor and idProduct values. Unique identifiers like serial numbers or Bluetooth device addresses MUST NOT be included in the id string.

index attribute

The index of the gamepad in the Navigator. When multiple gamepads are connected to a user agent, indices MUST be assigned on a first-come, first-serve basis, starting at zero. If a gamepad is disconnected, previously assigned indices MUST NOT be reassigned to gamepads that continue to be connected. However, if a gamepad is disconnected, and subsequently the same or a different gamepad is then connected, the lowest previously used index MUST be reused.

connected attribute

Indicates whether the physical device represented by this object is still connected to the system. When a gamepad becomes unavailable, whether by being physically disconnected, powered off or otherwise unusable, the connected attribute MUST be set to false.

The connected getter steps are:

1. Return this.[[connected]].

timestamp attribute

The timestamp allows the author to determine the last time the axes or buttons attribute for this gamepad was updated. The value MUST be set to the current high resolution time each time the system receives new button or axis input values from the device. If no data has been received from the hardware, timestamp MUST be the current high resolution time at the time when the Gamepad was first made available to script.

Warning

User agents SHOULD set a minimum resolution of the timestamp attribute to 5 microseconds, following [HR-TIME]'s clock resolution recommendation.

The timestamp getter steps are:

1. Return this.[[timestamp]].

mapping attribute

The mapping in use for this device. If the user agent has knowledge of the layout of the device, then it SHOULD indicate that a mapping is in use by setting mapping to the corresponding GamepadMappingType value.

To select a mapping for a gamepad device, run the following steps:

1. If the button and axis layout of the gamepad device corresponds with the Standard Gamepad layout, then return "standard".
2. Return "".

axes attribute

Array of values for all axes of the gamepad. All axis values MUST be linearly normalized to the range [-1 .. 1]. If the controller is perpendicular to the ground with the directional stick pointing up, -1 SHOULD correspond to "forward" or "left", and 1 SHOULD correspond to "backward" or "right". Axes that are drawn from a 2D input device SHOULD appear next to each other in the axes array, X then Y. It is RECOMMENDED that axes appear in decreasing order of importance, such that element 0 and 1 typically represent the X and Y axis of a directional stick. The same object MUST be returned until the user agent needs to return different values (or values in a different order).

The axes getter steps are:

1. Return this.[[axes]].

buttons attribute

Array of button states for all buttons of the gamepad. It is RECOMMENDED that buttons appear in decreasing importance such that the primary button, secondary button, tertiary button, and so on appear as elements 0, 1, 2, ... in the buttons array. The same object MUST be returned until the user agent needs to return different values (or values in a different order).

The buttons getter steps are:

1. Return this.[[buttons]].

touches attribute

A list of GamepadTouch objects generated from all touch surfaces.

The touches getter steps are:

1. Return this.[[touches]].

vibrationActuator attribute

A GamepadHapticActuator object that represents the device's primary vibration actuator.

The vibrationActuator getter steps are:

1. Return this.[[vibrationActuator]].

This interface defines the state of an individual button on a gamepad device.

[Exposed=Window]
interface GamepadButton {
  readonly attribute boolean pressed;
  readonly attribute boolean touched;
  readonly attribute double value;
};

Instances of GamepadButton are created with the internal slots described in the following table:

pressed attribute

The pressed state of the button. This property MUST be true if the button is currently pressed, and false if it is not pressed. For buttons which do not have a digital switch to indicate a pure pressed or released state, the user agent MUST choose a button press threshold to indicate the button as pressed when its value is above a certain amount. If the platform API gives a recommended value, the user agent SHOULD use that. In other cases, the user agent SHOULD choose some other reasonable value.

The pressed getter steps are:

1. Return this.[[pressed]].

touched attribute

The touched state of the button. If the button is capable of detecting touch, this property MUST be true if the button is currently being touched, and false otherwise. If the button is not capable of detecting touch and is capable of reporting an analog value, this property MUST be true if the value property is greater than 0, and false if the value is 0. If the button is not capable of detecting touch and can only report a digital value, this property MUST mirror the pressed attribute.

The touched getter steps are:

1. Return this.[[touched]].

value attribute

For buttons that have an analog sensor, this property MUST represent the amount which the button has been pressed. All button values MUST be linearly normalized to the range [0 .. 1]. 0 MUST mean fully unpressed, and 1 MUST mean fully pressed. For buttons without an analog sensor, only the values 0 and 1 for fully unpressed and fully pressed respectively, MUST be provided.

The value getter steps are:

1. Return this.[[value]].

This interface defines a touch on a gamepad's touch surface that supports such input. The object consists of a touch touchId that uniquely identifies the touch point from the time the input medium (e.g. finger, stylus, etc) makes contact with the touch device, up to the time the input medium is no longer making contact with the touch device.

dictionary GamepadTouch {
  unsigned long touchId;
  octet surfaceId;
  DOMPointReadOnly position;
  DOMRectReadOnly? surfaceDimensions;
};

touchId attribute

Unique id of the touch. Range is [0 .. 4294967295].

surfaceId attribute

Unique id of the surface that generated the touch.

position attribute

A DOMPointReadOnly which holds the x, y coordinates of the touch. The z and w value are currently unused. The range of each coordinate is normalized to [-1 .. 1]. Along the x-axis, -1 references the leftmost coordinate and 1 references the rightmost coordinate. Along the y-axis, -1 references the topmost coordinate and 1 references the bottommost coordinate.

surfaceDimensions attribute

A DOMRectReadOnly initialized with the width and height of the touch surface in integer units. If not available then null.

This enum defines the set of known mappings for a Gamepad.

enum GamepadMappingType {
  "",
  "standard",
  "xr-standard",
};

""

The empty string indicates that no mapping is in use for this gamepad.

" standard "

The Gamepad's controls have been mapped to the Standard Gamepad layout.

" xr-standard "

The Gamepad's controls have been mapped to the "xr-standard" gamepad mapping. This mapping is reserved for use by the WebXR Gamepads Module - Level 1. Gamepad objects returned by getGamepads() MUST NOT report a mapping of "xr-standard".

A GamepadHapticActuator corresponds to a configuration of motors or other actuators that can apply a force for the purposes of haptic feedback.

[Exposed=Window]
interface GamepadHapticActuator {
  [SameObject] readonly attribute FrozenArray<GamepadHapticEffectType> effects;
  Promise<GamepadHapticsResult> playEffect(
      GamepadHapticEffectType type,
      optional GamepadEffectParameters params = {}
  );
  Promise<GamepadHapticsResult> reset();
};

Instances of GamepadHapticActuator are created with the internal slots described in the following table:

effects attribute

Array of GamepadHapticEffectType values representing all the types of haptic effects that the actuator supports. This property lists the GamepadHapticEffectType values that the actuator supports, unless the user agent does not support playing effects of that type.

The effects getter steps are:

1. Return this.[[effects]].

playEffect() method

The playEffect() method steps, called with GamepadHapticEffectType type and GamepadEffectParameters params, are:

1. If params does not describe a valid effect of type type, return a promise rejected with a TypeError.
2. Let document be the current settings object's relevant global object's associated Document.
3. If document is null or document is not fully active or document's visibility state is "hidden", return a promise rejected with an "InvalidStateError" DOMException.
4. If this.[[playingEffectPromise]] is not null:
   1. Let effectPromise be this.[[playingEffectPromise]].
   2. Set this.[[playingEffectPromise]] to null.
   3. Queue a global task on the gamepad task source with the relevant global object of this to resolve effectPromise with "preempted".
5. If this GamepadHapticActuator cannot play effects with type type, return a promise rejected with reason NotSupportedError.
6. Let [[playingEffectPromise]] be a new promise.
7. Let playEffectTimestamp be the current high resolution time given the document's relevant global object.
8. Do the following steps in parallel:
   1. Issue a haptic effect to the actuator with type, params, and the playEffectTimestamp.
   2. When the effect completes, if this.[[playingEffectPromise]] is not null, queue a global task on the gamepad task source with the relevant global object of this to run the following steps:
      1. If this.[[playingEffectPromise]] is null, abort these steps.
      2. Resolve this.[[playingEffectPromise]] with "complete".
      3. Set this.[[playingEffectPromise]] to null.
9. Return [[playingEffectPromise]].

reset() method

The reset() method steps are:

1. Let document be the current settings object's relevant global object's associated Document.
2. If document is null or document is not fully active or document's visibility state is "hidden", return a promise rejected with an "InvalidStateError" DOMException.
3. Let resetResultPromise be a new promise.
4. If this.[[playingEffectPromise]] is not null, do the following steps in parallel:
   1. Let effectPromise be this.[[playingEffectPromise]].
   2. Stop haptic effects on this's gamepad's actuator.
   3. If the effect has been successfully stopped, do:
      1. If effectPromise and this.[[playingEffectPromise]] are still the same, set this.[[playingEffectPromise]] to null.
      2. Queue a global task on the gamepad task source with the relevant global object of this to resolve effectPromise with "preempted".
   4. Resolve resetResultPromise with "complete"
5. Return resetResultPromise.

A GamepadHapticActuator can play effects with type type if type can be found in the [[effects]] list.

To check if an effect with GamepadHapticEffectType type and GamepadEffectParameters params describes a valid effect , run the following steps:

1. Given the value of GamepadHapticEffectType type, switch on:

   "dual-rumble"

   If params does not describe a valid dual-rumble effect, return false.

   "trigger-rumble"

   If params does not describe a valid trigger-rumble effect, return false.

2. Return true

To issue a haptic effect on an actuator, the user agent MUST send a command to the device to render an effect of type and try to make it use the provided params. The user agent SHOULD use the provided playEffectTimestamp for more precise playback timing when params.startDelay is not 0.0. The user agent MAY modify the effect to increase compatibility. For example, an effect intended for a rumble motor may be transformed into a waveform-based effect for a device that supports waveform haptics but lacks rumble motors.

To stop haptic effects on an actuator, the user agent MUST send a command to the device to abort any effects currently being played. If a haptic effect was interrupted, the actuator SHOULD return to a motionless state as quickly as possible.

enum GamepadHapticsResult {
  "complete",
  "preempted"
};

complete

The haptic effected completed playing.

preempted

The current effect was stopped or replaced (i.e., "preempted") by another effect.

The effect type defines how the effect parameters are interpreted by the actuator.

enum GamepadHapticEffectType {
  "dual-rumble",
  "trigger-rumble"
};

" dual-rumble " effect type

"dual-rumble" describes a haptic configuration with an eccentric rotating mass (ERM) vibration motor in each handle of a standard gamepad. In this configuration, either motor is capable of vibrating the whole gamepad. The vibration effects created by each motor are unequal so that the effects of each can be combined to create more complex haptic effects.

A "dual-rumble" effect is a fixed-duration, constant-intensity vibration effect intended for an actuator of this type. "dual-rumble" effects are defined by startDelay, duration, strongMagnitude, and weakMagnitude, none of which are required because they default to 0.

strongMagnitude and weakMagnitude set the intensity levels for the low-frequency and high-frequency vibrations, normalized to the range [0 .. 1], defaulting to 0.

Given GamepadEffectParameters params, a valid dual-rumble effect must have a valid duration, a valid startDelay, and both the strongMagnitude and the weakMagnitude must be in the range [0 .. 1].

" trigger-rumble " effect type

"trigger-rumble" describes a haptics configuration with a vibration motor in each of the bottom front buttons of a Standard Gamepad (buttons with canonical indices 6 and 7) in addition to the two handle motors used for "dual-rumble". These buttons most commonly take the form of spring-loaded triggers. In this configuration, either motor is capable of providing localized haptic feedback on the button's surface.

A "trigger-rumble" effect is a fixed-duration, constant-intensity vibration effect intended for an actuator of this type. "trigger-rumble" effects are defined by startDelay, duration, strongMagnitude, weakMagnitude, leftTrigger, and rightTrigger, none of which are required because they default to 0.

startDelay, duration, strongMagnitude, weakMagnitude share the same definition with "dual-rumble". leftTrigger and rightTrigger, respectively, set the intensity levels for the left and right bottom front buttons vibrations, normalized to the range [0 .. 1], defaulting to 0.

Given GamepadEffectParameters params, a valid trigger-rumble effect must have a valid duration, a valid startDelay, and the strongMagnitude, weakMagnitude, leftTrigger, and rightTrigger must be in the range [0 .. 1].

A GamepadEffectParameters dictionary contains keys for parameters used by haptic effects. The meaning of each key is defined by the haptic effect, and some keys may be unused.

To mitigate unwanted long-running effects, the user agent MAY limit the total effect duration for a valid effect to some maximum duration. It is RECOMMENDED that the user agent use a maximum of 5 seconds.

dictionary GamepadEffectParameters {
    unsigned long long duration = 0;
    unsigned long long startDelay = 0;
    double strongMagnitude = 0.0;
    double weakMagnitude = 0.0;
    double leftTrigger = 0.0;
    double rightTrigger = 0.0;
};

duration member

duration sets the duration of the vibration effect in milliseconds.

startDelay member

startDelay sets the duration of the delay after playEffect() is called until vibration is started, in milliseconds. During the delay interval, the actuator SHOULD NOT vibrate.

strongMagnitude member

The vibration magnitude for the low frequency rumble in a "dual-rumble" or "trigger-rumble" effect.

weakMagnitude member

The vibration magnitude for the high frequency rumble in a "dual-rumble" or "trigger-rumble" effect.

leftTrigger member

The vibration magnitude for the bottom left front button (canonical index 6) rumble in a "trigger-rumble" effect.

rightTrigger member

The vibration magnitude for the bottom right front button (canonical index 7) rumble in a "trigger-rumble" effect.

[Exposed=Window]
partial interface Navigator {
  sequence<Gamepad?> getGamepads();
};

Instances of Navigator are created with the internal slots described in the following table:

[Exposed=Window]
interface GamepadEvent: Event {
   constructor (DOMString type, GamepadEventInit eventInitDict);
  [SameObject] readonly attribute Gamepad gamepad;
};

gamepad attribute

The gamepad attribute provides access to the associated gamepad data for this event.

dictionary GamepadEventInit : EventInit {
  required Gamepad gamepad;
};

Each device manufacturer creates many different products and each has unique styles and layouts of buttons and axes. It is intended that the user agent support as many of these as possible.

Additionally there are de facto standard layouts that have been made popular by game consoles. When the user agent recognizes the attached device, it is RECOMMENDED that it be remapped to a canonical ordering when possible. Devices that are not recognized should still be exposed in their raw form.

There is currently one canonical layout, the Standard Gamepad . When remapping, the indices in axes and buttons should correspond as closely as possible to the physical locations in the diagram below. Additionally, mapping SHOULD be set to "standard".

The Standard Gamepad buttons are laid out in a left cluster of four buttons, a right cluster of four buttons, a center cluster of three buttons, and a pair of front facing buttons on the left and right side of the gamepad. The four axes of the "Standard Gamepad" are associated with a pair of analog sticks, one on the left and one on the right. The following table describes the buttons/axes and their physical locations.

An axis input represents a Standard Gamepad axis if it reports the input value for a thumbstick axis, the thumbstick is located in approximately the same location as the corresponding Standard Gamepad thumbstick, and the orientation of the axis (up-down or left-right) matches the orientation of the Standard Gamepad axis. If there are multiple axes that represent the same Standard Gamepad axis, then the user agent SHOULD select one to be the Standard Gamepad axis and assign a different index to the other axis.

A button input represents a Standard Gamepad button if it reports the input value for a button or trigger, and the button or trigger is located in approximately the same location as the corresponding Standard Gamepad button.

If an axis or button input represents a Standard Gamepad axis or button, then its canonical index is the index of the corresponding Standard Gamepad axis or button.

This section is non-normative.

The example below demonstrates typical access to gamepads. Note the relationship with the requestAnimationFrame() method.

function runAnimation() {
    window.requestAnimationFrame(runAnimation);
    for (const pad of navigator.getGamepads()) {
      // todo; simple demo of displaying pad.axes and pad.buttons
      console.log(pad);
    }
}
window.requestAnimationFrame(runAnimation);

When a gamepad becomes available on the system, run the following steps:

1. Let document be the current global object's associated Document; otherwise null.
2. If document is not null and is not allowed to use the "gamepad" permission, then abort these steps.
3. Queue a global task on the gamepad task source with the current global object to perform the following steps:
   1. Let gamepad be a new Gamepad representing the gamepad.
   2. Let navigator be gamepad's relevant global object's Navigator object.
   3. Set navigator.[[gamepads]][gamepad.index] to gamepad.
   4. If navigator.[[hasGamepadGesture]] is true:
      1. Set gamepad.[[exposed]] to true.
      2. If document is not null and is fully active, then fire an event named gamepadconnected at gamepad's relevant global object using GamepadEvent with its gamepad attribute initialized to gamepad.

User agents implementing this specification must provide a new DOM event, named gamepadconnected. The corresponding event MUST be of type GamepadEvent and MUST fire on the Window object.

A user agent MUST dispatch this event type to indicate the user has connected a gamepad. If a gamepad was already connected when the page was loaded, the gamepadconnected event SHOULD be dispatched when the user presses a button or moves an axis.

When a gamepad becomes unavailable on the system, run the following steps:

1. Let gamepad be the Gamepad representing the unavailable device.
2. Queue a global task on the gamepad task source with gamepad's relevant global object to perform the following steps:
   1. Set gamepad.[[connected]] to false.
   2. Let document be gamepad's relevant global object's associated Document; otherwise null.
   3. If gamepad.[[exposed]] is true and document is not null and is fully active, then fire an event named gamepaddisconnected at gamepad's relevant global object using GamepadEvent with its gamepad attribute initialized to gamepad.
   4. Let navigator be gamepad's relevant global object's Navigator object.
   5. Set navigator.[[gamepads]][gamepad.index] to null.
   6. While navigator.[[gamepads]] is not empty and the last item of navigator.[[gamepads]] is null, remove the last item of navigator.[[gamepads]].

User agents implementing this specification must provide a new DOM event, named gamepaddisconnected. The corresponding event MUST be of type GamepadEvent and MUST fire on the Window object.

When a gamepad is disconnected from the user agent, if the user agent has previously dispatched a gamepadconnected event for that gamepad to a Window, a gamepaddisconnected event MUST be dispatched to that same Window.

More discussion needed, on whether to include or exclude axis and button changed events, and whether to roll them more together ("gamepadchanged"?), separate somewhat ("gamepadaxischanged"?), or separate by individual axis and button.

This specification extends the WindowEventHandlers interface mixin from HTML to add event handler IDL attributes to facilitate the event handler registration.

partial interface mixin WindowEventHandlers {
  attribute EventHandler  ongamepadconnected ;
  attribute EventHandler  ongamepaddisconnected ;
};

This specification defines a policy-controlled feature identified by the string "gamepad" . Its default allowlist is *.

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, MUST NOT, RECOMMENDED, SHOULD, and SHOULD NOT in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

This section is non-normative.

The following people contributed to the development of this document.

• Anssi Kostiainen
• Arthur Barstow
• autokagami
• Bradley Needham
• Brandon Jones
• Chris Wilson
• Christopher Van Wiemeersch
• ddorwin
• fernando-80
• fernando-sony
• Gabriel Brito
• James
• Johanna
• Kagami Sascha Rosylight
• Kelvin Yong
• kri
• Marcos Cáceres
• Michael Blix
• Mike Taylor
• Philip Jägenstedt
• Philippe Le Hegaret
• Scott Graham
• Sid Vishnoi
• stephen
• Ted Mielczarek
• Vincent Scheib
• Xiaoqian Wu
• Yves Lafon

[dom]

DOM Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://dom.spec.whatwg.org/

[FINGERPRINTING-GUIDANCE]

Mitigating Browser Fingerprinting in Web Specifications. Nick Doty; Tom Ritter. W3C. 21 March 2025. W3C Working Group Note. URL: https://www.w3.org/TR/fingerprinting-guidance/

[geometry-1]

Geometry Interfaces Module Level 1. Simon Pieters; Chris Harrelson. W3C. 4 December 2018. W3C Candidate Recommendation. URL: https://www.w3.org/TR/geometry-1/

[HR-TIME]

High Resolution Time. Yoav Weiss. W3C. 7 November 2024. W3C Working Draft. URL: https://www.w3.org/TR/hr-time-3/

[html]

HTML Standard. Anne van Kesteren; Domenic Denicola; Dominic Farolino; Ian Hickson; Philip Jägenstedt; Simon Pieters. WHATWG. Living Standard. URL: https://html.spec.whatwg.org/multipage/

[infra]

Infra Standard. Anne van Kesteren; Domenic Denicola. WHATWG. Living Standard. URL: https://infra.spec.whatwg.org/

[permissions-policy]

Permissions Policy. Ian Clelland. W3C. 6 May 2025. W3C Working Draft. URL: https://www.w3.org/TR/permissions-policy-1/

[RFC2119]

Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119

[RFC8174]

Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174

[WEBIDL]

Web IDL Standard. Edgar Chen; Timothy Gu. WHATWG. Living Standard. URL: https://webidl.spec.whatwg.org/

[webxr-gamepads-module-1]

WebXR Gamepads Module - Level 1. Brandon Jones; Manish Goregaokar; Rik Cabanier. W3C. 9 April 2024. W3C Working Draft. URL: https://www.w3.org/TR/webxr-gamepads-module-1/