Exiting WebXR minimizes the oculus browser
We have a product using threejs and aframe. One of the features lets you redirect to a non xr site. For this we call `xrSession.end()` to end the xr and redirect to the new page. This did work up until recently. Now whenever `xrSession.end()` is called the user finds themself with a minimized browser. I belive this is due to the recent update of the Oculus Browser. Is there something I need to think about before calling `xrSession.end()` or might this be a new bug introduced by accident?
Oculus Browser Release Notes
I primarily develop WebXR apps for the Oculus Browser and try to keep an eye on any new standards and features being implemented in the Oculus Browser that may effect my workflow. This involves reading the release notes for each update. Currently on Oculus Browser 16.4 but the developer release notes haven't updated since 16.2 and the user release notes haven't been updated since 15.0 Are the release notes at https://developer.oculus.com/documentation/oculus-browser/browser-release-notes/ no longer being updated? Is there another link I should be monitoring?
“speechSynthesis is not defined” Uncaught ReferenceError in Oculus browser
Text to Speach API demo function speak() { speechSynthesis.speak(new SpeechSynthesisUtterance("hello world")); } works in Chrome on Windows and Android but I get "Uncaught ReferenceError: speechSynthesis is not defined" in the Oculus browser. Can I use TTS API in the Oculus browser?
Audio Issues in Oculus Browser on Quest & Go
I'm not sure if this is the right place to discuss this issue. If not, please point to the right place. I'm working on some WebXR ideas using A-Frame version 1.0.4. I can a basic scene setup here. When the scene loads it starts playback on some ambient music. When I visit this scene in the Oculus Browser that ships with Oculus Quest and Go I can hear the audio when the page loads. Before I enter VR mode the audio sounds correct, but when I enter VR mode the audio is distorted. It's hard to explain what I'm hearing. I can still hear the music, but there is this constant cracking/static sound as well. If I "back out" of VR mode to the Oculus Home environment with the browser window, the distortion stops. I'm not getting this audio distortion on any other platform. Audio is working as expected on all PC VR headsets and browsers that I have access to. It is also working as expected in Firefox Reality on Oculus Quest. From what I can tell, this issue has something to do with the built-in Oculus Browser. Can anyone here provide any direction for addressing or further troubleshooting this issue. Is there a specific place I can file a bug report for the Oculus Browser team?
[WebVR] [Oculus Go] Headset and Controller have different display ids
Hello, we have developed a 360° showcase web app and implemented the web vr interface. We have already tested the website in Firefox with the Vive and Rift and on Android with the Google Daydream. When we tested the app with Oculus Go we noticed that the vr api works as indented but the controller was missing. I debugged the browser app and found this: The display id of the Oculus Go and the display id of the controller were different. When the controller is in the same 3d space as the vr headset the two display ids should match. This is not the case when using the Oculus Browser. So our web app ignores the controller. See also: https://developer.mozilla.org/en-US/docs/Web/API/Gamepad/displayId Here is an example: https://webvr.info/samples/XX-vr-controllers.html This app ignores the display id so the controller is visible. Open this link in the Oculus Go. Connect your Oculus Go to your computer, enable developer mode and install ADB. Open Chrome on your Desktop and enter chrome://inspect. Inspect the XX - VR Controllers tab. List all your vr displays with "navigator.getVRDisplays().then((r) => console.log(r))". List all your gamepads with "navigator.getGamepads()". You should see that the display ids differ. For now we'll ignore the display id if the display name is "Oculus Go". But is this behaviour indented or is this a bug? The ids match in the Android Chrome browser.
