Better handling of images not served over HTTPS

[azw413]

I've tried a few SBS 3D images and I always get the same result: views fine in non-VR mode but the 'Enter VR' mode doesn't seem to enter the WebXR mode and instead just displays a binocular stereo view with image data only in the left eye, which does respond to headset movement but the right eye is empty and it just doesn't enter the WebXR view so there's no 3D visualisation. Here's two examples, one a VR180 fisheye SBS image from a Insta360 Evo and a non VR-180 3d image from a Sony Bloggie 3d camera. Example code :-

<stereo-img src="media/bloggie.jpg" wiggle="false"></stereo-img>

[steren]

Thanks, what browser are you using ?

[azw413]

It's Wolvic on HTC Vive Flow. Your Qoocam and Lenovo Mirage VR180 images render fine in WebXR mode on that device. I'll retest on the Meta Browser and Wolvic on Oculus Quest and report back.

[azw413]

On Oculus Quest: Your Lenovo Mirage image displays correctly in both MetaBrowser and Wolvic. The SBS 3D image 'bloggie' above, behaves the same as the above description on Wolvic and on MetaBrowser, it says 'VR Mode not available' on the button. My thoughts are that SBS images are just not triggering the WebXR scene for some reason. Thanks

[azw413]

I figured it out, it only works if served over a HTTPS connection! Strangely though your Lenovo Mirage image worked fine over HTTP. No idea why that may be but I only discovered it when looking for alternatives using AFrame and there it mandated HTTPS. So there's no bug, just a limitation that people need to be aware of. Thanks!

[steren]

Thanks for sharing.

I think I could print a clear warning in the dev console if the image isn't served from HTTPS

[steren]

TODO: ensure proper error messages (at least in the console) when the image cannot be parsed because not served over HTTPS