Hi fellow Chromium developers,
Oculus ships a Chromium-based browser that supports WebXR. It's really neat to be able to browse to web pages in-device and try immersive experiences without installing full-blown applications!
Several sites I've tried offer up their content over both http and https. https is required for the page to use the WebXR API, a powerful web feature. On these sites, typing the URL without a scheme goes to the http version. Then the URL has to be manually edited to change it to "https".
A couple of examples:
(Try copy/pasting the text of these links into Chromium's Omnibox so that they don't include a URL scheme - they use http, even though the servers offer https.)
It would be great if Chromium could try https first, though I'm sure there are pitfalls.
The Oculus Browser engineers recall that this behavior (try https first, fall back to http under circumstances like certificate errors) was proposed at one point but concerns were raised. Does anyone remember the context of that conversation? I couldn't easily find it via email or web searches.
Thanks,
-Ken