XRSystem
Secure context: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.
Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The WebXR Device API interface XRSystem
provides methods which let you get access to an XRSession
object representing a WebXR session. With that XRSession
in hand, you can use it to interact with the Augmented Reality (AR) or Virtual Reality (VR) device.
Instance properties
While XRSystem
directly offers no properties, it does inherit properties from its parent interface, EventTarget
.
Instance methods
In addition to inheriting methods from its parent interface, EventTarget
, the XRSystem
interface includes the following methods:
isSessionSupported()
Experimental-
Returns a promise which resolves to
true
if the browser supports the given session mode. Resolves tofalse
if the specified mode isn't supported. requestSession()
Experimental-
Returns a promise that resolves to a new
XRSession
with the specified session mode.
Events
devicechange
Experimental-
Sent when the set of available XR devices has changed. Also available using the
ondevicechange
event handler.
Usage notes
This interface was previously known as XR
in earlier versions of the specification; if you see references to XR
in code or documentation, replace that with XRSystem
.
Examples
The following example shows how to use both isSessionSupported()
and requestSession()
.
js
if (navigator.xr) {
immersiveButton.addEventListener("click", onButtonClicked);
navigator.xr.isSessionSupported("immersive-vr").then((isSupported) => {
immersiveButton.disabled = !isSupported;
});
}
function onButtonClicked() {
if (!xrSession) {
navigator.xr.requestSession("immersive-vr").then((session) => {
// onSessionStarted() not shown for reasons of brevity and clarity.
onSessionStarted(session);
});
} else {
// Shut down the already running XRSession
xrSession.end().then(() => {
// Since there are cases where the end event is not sent, call the handler here as well.
onSessionEnded();
});
}
}
This code starts by checking to see if WebXR is available by looking for the navigator.xr
property. If it's found, we know WebXR is present, so we proceed by establishing a handler for the button which the user can click to toggle immersive VR mode on and off.
However, we don't yet know if the desired immersive mode is available. To determine this, we call isSessionSupported()
, passing it the desired session option before enabling the button, immersiveButton
, which the user can then use to switch to immersive mode only if immersive VR mode is available. If immersive VR isn't available, the button is disabled to prevent its use.
The onButtonClicked()
function checks to see if there's already a session running. If there isn't, we use requestSession()
to start one and, once the returned promise resolves, we call a function onSessionStarted()
to set up our session for rendering and so forth.
If, on the other hand, there is already an ongoing XR session, we instead call end()
to end the current session. When the current session ends, the end
event is sent, so set xrSession
to null
in its handler to record the fact that we no longer have an ongoing session. That way, if the user clicks the button again, a new session will start.
Specifications
Specification |
---|
WebXR Device API # xrsystem-interface |
Browser compatibility
BCD tables only load in the browser