VRDisplayCapabilities.canPresent

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 canPresent read-only property of the VRDisplayCapabilities interface returns a boolean value stating whether the VR display is capable of presenting content (e.g. through an HMD).

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

This is useful for identifying "magic window" devices that are capable of 6DoF tracking but for which VRDisplay.requestPresent() is not meaningful. If canPresent is false, calls to VRDisplay.requestPresent() will fail, and VRDisplay.getEyeParameters() will return null.

Value

A boolean value.

Examples

See VRDisplayCapabilities for example code.

Specifications

This property 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

See also