The issue may require a VR device to be tested with. With no VR device, observed same behavior i.e the blue button showed 'VR NOT FOUND' and a DOMException is thrown in console in latest chrome version #71.0.3548.0, latest stable #69.0.3497.92 and M-67.

As ET team doesn't have a VR to test the issue. Hence, adding TE-Hardware-Dependency label and removing Needs-Bisect label.

Thanks...!!

Ah yes sorry, I should have mentioned that I have a vive connected.

I just realised though, it is possible to reproduce this partially without a vive.
Even though the button will always say 'VR NOT FOUND' when I have my vive disconnected, SteamVR will still start up on page load. As long as SteamVR is installed at least.
So where in Chrome 69 it starts SteamVR on page load, it doesn't in Chrome 71.

So perhaps this can be fixed without hardware, though I'm not familiar with the Chromium codebase so I might be completely wrong.

Are you still able to reproduce this issue on the latest Chrome Canary or Dev- Chrome 71 or Chrome 72?

I haven't been able to reproduce the issue so far in testing.

There was a problem earlier with running OpenVR in the browser process conflicting with recent security changes to block third-party modules from running in the browser process.  The fix (running OpenVR in a utility process) landed on September 18, after this was filed.  I strongly suspect this was the issue, so resolving as "fixed", but please reactivate if you see issues still.

I'm no longer able to reproduce this either, so I suppose it's fixed. I can't say that with 100% certainty though since it was starting SteamVR successfully in the past a couple of times as well. But I think it's safe to say this has been fixed.