VRDisplayCapabilities
=====================

**Deprecated:** This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

**Non-standard:** This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

The **`VRDisplayCapabilities`** interface of the WebVR API describes the capabilities of a `VRDisplay` — its features can be used to perform VR device capability tests, for example can it return position information.

**Note:** This interface was part of the old WebVR API. It has been superseded by the WebXR Device API.

This interface is accessible through the `VRDisplay.capabilities` property.

Instance properties
-------------------

`VRDisplayCapabilities.canPresent` 
Deprecated
 Read only  
Non-standard

Returns a boolean value stating whether the VR display is capable of presenting content (e.g. through an HMD).

`VRDisplayCapabilities.hasExternalDisplay` 
Deprecated
 Read only  
Non-standard

Returns a boolean value stating whether the VR display is separate from the device's primary display.

`VRDisplayCapabilities.hasOrientation` 
Deprecated
 Read only  
Non-standard

Returns a boolean value stating whether the VR display can track and return orientation information.

`VRDisplayCapabilities.hasPosition` 
Deprecated
 Read only  
Non-standard

Returns a boolean value stating whether the VR display can track and return position information.

`VRDisplayCapabilities.maxLayers` 
Deprecated
 Read only  
Non-standard

Returns a number indicating the maximum number of `VRLayerInit`s that the VR display can present at once (e.g. the maximum length of the array that `VRDisplay.requestPresent()` can accept.)

Examples
--------


```js
function reportDisplays() {
  navigator.getVRDisplays().then((displays) => {
    displays.forEach((display, i) => {
      const cap = display.capabilities;
      // cap is a VRDisplayCapabilities object
      const listItem = document.createElement("li");
      listItem.innerHTML =
        `<strong>Display ${i + 1}</strong><br>` +
        `VR Display ID: ${display.displayId}<br>` +
        `VR Display Name: ${display.displayName}<br>` +
        `Display can present content: ${cap.canPresent}<br>` +
        `Display is separate from the computer's main display: ${cap.hasExternalDisplay}<br>` +
        `Display can return position info: ${cap.hasPosition}<br>` +
        `Display can return orientation info: ${cap.hasOrientation}<br>` +
        `Display max layers: ${cap.maxLayers}`;
      list.appendChild(listItem);
    });
  });
}
```

Specifications
--------------

This interface was part of the old WebVR API that has been superseded by the WebXR Device API. It is no longer on track to becoming a standard.

Until all browsers have implemented the new WebXR APIs, it is recommended to rely on frameworks, like A-Frame, Babylon.js, or Three.js, or a polyfill, to develop WebXR applications that will work across all browsers [1].

Browser compatibility
---------------------

BCD tables only load in the browser with JavaScript enabled. Enable JavaScript to view data.

See also
--------

* WebVR API