[Affected versions]: - Firefox 55 beta 10 [Affected platforms]: - Windows 10 64/32bit [Steps to reproduce]: 1. Launch Fx and go to https://aframe.io/a-painter/ . 2. Click from the page the VR button. 3. Open a new tab. 4. Close the VR page. [Expected result]: - The user is notified about the disrupt. [Actual result]: - The VR displays the last recorded image. [Regression range]: - This is not a regression as this feature is new. [Additional notes]: - It should check periodically the signal and warn the user if any lost connection is met.
The headset is expected to be blanked when you close the tab. The logic to implement this is unique to Oculus and HTC Vive. Please advise which one was in use.
Behavior in each headset: - Oculus Rift: After closing the tab the Oculus screen with the hourglass is displayed indefinitely. - HTC Vive: After closing the tab Steam VR loading screen is rendered indefinitely.
(In reply to Diego Marcos [:dmarcos] from comment #2) > Behavior in each headset: > > - Oculus Rift: After closing the tab the Oculus screen with the hourglass is > displayed indefinitely. > - HTC Vive: After closing the tab Steam VR loading screen is rendered > indefinitely. Thanks for testing Diego. For Oculus, there should be a 30 second timeout (configurable via a pref), after which time the black screen with the hourglass will automatically dismiss and return you to Oculus home. It should also be possible to return to Oculus home immediately at any time using the Oculus touch controller or XBox controller home buttons.
Re: HTC Vive behavior, the runtime used to automatically return you to your default space when it no longer received any frames. Perhaps this behavior has changed recently and should be revisited. We should also test the HTC Vive with SteamVR Beta, which changes the way home environments work.
I confirm that you can go back to the Oculus or Steam Home by pressing the respective buttons.
The Oculus Rift timeout to go to the Home space from the hourglass is not working for me. I get stuck with the hourglass
I was able to reproduce this with an Oculus CV1 and 55.0b10 (64-bit) Updating to 55.0b12 (64-bit) resolved the issue for Oculus. I have not yet verified for HTC Vive.
I will verify the issue on both Vive and Oculus on both Nightly and beta 12/13 as soon as possible.
I re-tested using Fx 55.0b13. Refreshing the page causes the Oculus to be turned off, after the user selects Enter VR the experience is no longer jerky. Vive goes into their VR room but after clicking the enter VR button the demo it goes fine.
Based on Comment 9, I'll mark this as fixed. If you still see this happen, please file a new bug or re-open this one.
I re-verified using Fx 57.0b5 and Fx 58.0a1 (build ID: 20171004100049) on Windows 10 x64 and I can confirm this issue is fixed.