[Bug]: WebXR API not working

[acceleratxr]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

19.0.8

What operating system are you using?

Windows

Operating System Version

Windows 11 Pro 22000.795

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

Using the WebXR API successfully detects 'immersive-vr' as being supported.

The following is our react-based application running in Chrome version 103.

Actual Behavior

Using the WebXR API does not detect 'immersive-vr' as being supported.

Testcase Gist URL

No response

Additional Information

I was able to reproduce this behavior using Electron v19.0.8, v20.0.0-beta10, and a custom v21 nightly build with checkout_openxr explicitly set to True. I have also tried explicitly disabling the sandbox mode for the browser window as shown in the example below...

mainWindow = new BrowserWindow({
            backgroundColor: "#000",
            frame: false,
            width: Store.has("win.width") ? Store.get("win.width") : MIN_WIN_WIDTH,
            height: Store.has("win.height") ? Store.get("win.height") : MIN_WIN_HEIGHT,
            x: Store.has("win.x") ? Store.get("win.x") : undefined,
            y: Store.has("win.y") ? Store.get("win.y") : undefined,
            minWidth: MIN_WIN_WIDTH,
            minHeight: MIN_WIN_HEIGHT,
            webPreferences: {
                contextIsolation: false,
                nodeIntegration: false,
                preload: __dirname + "/preload.js",
                sandbox: false
            },
        });

Test code for detecting the VR support is as follows...

const [vrSupported, setVRSupported] = useState(true);

    useEffect(() => {
        if ("xr" in navigator) {
            //@ts-ignore
            navigator.xr.isSessionSupported('immersive-vr')
                .then((isSupported: boolean) => {
                    setVRSupported(isSupported);
                });
        }
    }, []);

[MarshallOfSound]

Per https://releases.electronjs.org/ Electron 19 is based on M102, can you try Electron 20 beta which is based on M104 and therefore will more likely align with your testcase of Chrome M103

[acceleratxr]

Per https://releases.electronjs.org/ Electron 19 is based on M102, can you try Electron 20 beta which is based on M104 and therefore will more likely align with your testcase of Chrome M103

As already noted in the additional information.

"I was able to reproduce this behavior using Electron v19.0.8, v20.0.0-beta10, and a custom v21 nightly build with checkout_openxr explicitly set to True."

[rdumouchelle]

@MarshallOfSound Per above, this isn't blocked. Can the tags be updated accordingly? Thank you.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[rdumouchelle]

This is still occurring and needs support

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[rdumouchelle]

Still occurring.

@MarshallOfSound as described in original comment: #35011 (comment) -- the repro is described here. The blocked/need more info label should be able to be removed; if not please comment on the ticket what more is needed.

[samrun0]

Any updates on this issue, and in order to enable webXR for ElectronJS?

[cyberneticocult]

Pretty good blog post about this topic. https://bai.dev/projects/webxr-electron-apr2021.html

The main point being OpenXR is not included in the build of Electron so the WebXR api is disabled.
Electron DEPS File

You can either make a local build of Electron like in the post or use NW.js which has WebXR enabled.
NW.js DEPS File

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[rdumouchelle]

Still occurring.

[alexpineda]

I'm not having any luck either. Working on a 3d renderer for the original StarCraft and my dream is to have VR work with it. The devices aren't being found, even with the same example working in Chrome. I'm using the ThreeJS VRButton, who's examples can be seen here: https://threejs.org/examples/?q=vr#webxr_vr_handinput

I'm using Oculus 2 with link cable. SteamVR works, other browser examples work, electron doesn't :( Any pointers would be great. I did try adding the ACLs on the executable directory.

The default DEPS build should work since I'm on windows:

  # By default checkout the OpenXR loader library only on Windows and Android.
  # The OpenXR backend for VR in Chromium is currently only supported for these
  # platforms, but support for other platforms may be added in the future.
  'checkout_openxr' : 'checkout_win or checkout_android'

I also tried hardcoding it in my own build but no luck

'checkout_openxr' : True,

I've validated that I'm running in a secure context:

isSecureContext === true

and navigator.xr is present

[cyberneticocult]

@alexpineda You're probably running into the same issue that @jbaicoianu did with the access control lists (ACLs).
I would give the blog post a read through, it's pretty detailed. https://bai.dev/projects/webxr-electron-apr2021.html

[electron-issue-triage]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[yuripourre]

Bump

[electron-issue-triage]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

[yuripourre]

bump