10-08-2024 08:12 AM
Is there any way to detect user presence in the built-browser on the Quest 3 via WebXR, aka detect when the headset is on someone's head? When removing the headset in our WebXR app, the display of the Quest 3 does indeed turn off as expected, but the WebXR Session does not fire its visibilitychange event until the Quest sleeps (about 10 seconds later). Could the event fire when the headset is removed?
Or if not, could the browser fire an inputchange event when the headset is removed, and list the proximity sensor as an input?
My company use WebXR for streaming 360 video and other assets, and we want to be able to pause the experience the moment the headset is removed. Our goal is to get to feature parity with our desktop VR app so we can transition our customers onto Quest 3, and for that we need to be able to detect user presence.
10-15-2024 11:11 AM
Hey folks, any movement or input on this? Is this topic better for the Quest Development board since it surrounds the browser?
10-17-2024 10:03 AM
Thanks for raising this. We will be updating the browser to fire the visibilitychange event when the device is doffed.
10-24-2024 12:27 PM
Thank you! This will really help a lot. I'll be sure to mark this as an accepted solution once the browser is updated 👍
03-06-2025 03:15 PM
Following up again (this is my actual username for the company). What's the status of this? Also, is there a way to figure out when the user switches out of the webxr app and back to the window, via the system's pinch gesture? Furthermore, is there a way to ignore this gesture so the user stays in the webxr app?