To check, if “https” is used, I searched it in the document.location for it.
If it is missing, a message “no WebXR” could be extended to “no WebXR, no HTTPS used!”
Drawing an error or using the log will not help stupid coders like me, testing in a VR/AR device without remote debugging. The only way seems to draw an alert(message).
The application code should handle both cases and avoid the babylon-alert this way.
To to so, Babylon could offer something like “checkReality()”, returning an structure of booleans:
https, webxr, webvr, touchcontrols, orientationcontrols (3df), positioncontrols (6df), handcontrolers, webAR
and the other optional functionalities of webxr.
I myselves consider to check https in index.html and restart it, adding this option
to overrool the “wrong” user URL.