Feature-Policy: vr

This is an experimental technology
Check the Browser compatibility table carefully before using this in production.

The WebVR API has been replced with the WebXR Device API and is currently being removed from the web platform. Use the feature identifier xr-spatial-tracking for WebXR Device API instead.

The HTTP Feature-Policy header vr directive controls whether the current document is allowed to use the WebVR API. When this policy is enabled, the Promise returned by Navigator.getVRDisplays() will reject with a DOMException.

Syntax

Feature-Policy: vr <allowlist>;
<allowlist>

An allowlist is a list of origins that takes one or more of the following values, separated by spaces:

  • *: The feature will be allowed in this document, and all nested browsing contexts (iframes) regardless of their origin.
  • 'self': The feature will be allowed in this document, and in all nested browsing contexts (iframes) in the same origin.
  • 'src': (In an iframe allow attribute only) The feature will be allowed in this iframe, as long as the document loaded into it comes from the same origin as the URL in the iframe's src attribute.
    The 'src' origin is used in the iframe allow attribute only, and is the default allowlist value. 
  • 'none': The feature is disabled in top-level and nested browsing contexts.
  • <origin(s)>: The feature is allowed for specific origins (for example, https://example.com). Origins should be separated by a space.

The values * (enable for all origins) or 'none' (disable for all origins) may only be used alone, while 'self' and 'src' may be used with one or more origins.

Features are each defined to have a default allowlist, which is one of:

  • *: The feature is allowed by default in top-level browsing contexts and all nested browsing contexts (iframes).
  • 'self': The feature is allowed by default in top-level browsing contexts and in nested browsing contexts (iframes) in the same origin. The feature is not allowed in cross-origin documents in nested browsing contexts.
  • 'none': The feature is disabled in top-level and nested browsing contexts.

Default policy

The default allowlist is 'self'.

Specifications

Specification Status Comment
Permissions Policy Editor's Draft Initial definition.
WebVR 1.1 Draft

Browser compatibility

Update compatibility data on GitHub
DesktopMobile
ChromeEdgeFirefoxInternet ExplorerOperaSafariAndroid webviewChrome for AndroidFirefox for AndroidOpera for AndroidSafari on iOSSamsung Internet
vr
ExperimentalDeprecated
Chrome No support 62 — 80
Notes
No support 62 — 80
Notes
Notes WebVR API was never enabled by default in any production builds and was replaced by WebXR Device API.
Edge No support 79 — 80
Notes
No support 79 — 80
Notes
Notes WebVR API was never enabled by default in any production builds and was replaced by WebXR Device API.
Firefox No support NoIE No support NoOpera No support 49 — 67
Notes
No support 49 — 67
Notes
Notes WebVR API was never enabled by default in any production builds and was replaced by WebXR Device API.
Safari No support NoWebView Android No support NoChrome Android No support 62 — 80
Notes
No support 62 — 80
Notes
Notes WebVR API was never enabled by default in any production builds and was replaced by WebXR Device API.
Firefox Android No support NoOpera Android No support 46 — ?
Notes
No support 46 — ?
Notes
Notes WebVR API was never enabled by default in any production builds and was replaced by WebXR Device API.
Safari iOS No support NoSamsung Internet Android No support 8.0 — ?
Notes
No support 8.0 — ?
Notes
Notes WebVR API was never enabled by default in any production builds and was replaced by WebXR Device API.

Legend

No support  
No support
Experimental. Expect behavior to change in the future.
Experimental. Expect behavior to change in the future.
Deprecated. Not for use in new websites.
Deprecated. Not for use in new websites.
See implementation notes.
See implementation notes.

See also