Thanks for filing the issue!

Checked the issue on reported chrome version 66.0.3350.0 and on the latest stable 64.0.3282.167 using Windows 10 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://webvr.info/samples/03-vr-presentation.html
It shows an error message saying the browser doesn't support WebVR. Attaching the screen shot of the same for reference.

@Reporter: Could you please check the screen shot and let us know if anything missed. Any further inputs from your end helps us to triage the issue in a better way.

Deleted: 813355.PNG 1.6 MB

	813355.PNG 1.6 MB View Download

You will probably need to send this to the VR team (?billorr) as without the appropriate hardware you won't be able to check.  I should have made that clearer, sorry.

Extra step in Chrome after 1 (the VR team will know anyway)
1a. enter chrome://flags
1b. filter on VR: enable WebVR, WebXR, OpenVR
1c. filter on gamepad: enable gamepads
1d. restart Chrome

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment#3 by reporter adding component "Internals>VR", label TE-Hardware-Dependency and assigning it to "billorr".

@billorr: Could you please have a look into this issue and help in triaging it further.

Thanks!

It may (or may not) help to know the background.

We run VR in exhibitions with no mouse or keyboard available; machine startup logs in the user and starts the WebVR app.
In order to enter VR mode we fire simulated keystrokes at the WebVR app (an --allow-vr-without-user-interaction Chrome flag would be better).
We used to use tab to make sure the correct part of the window was ready to accept the 'main' keystroke, and that sometimes froze the app.
I now see that using F6 works better anyway and does not seem to have the freeze issue, so from our point of view this tab bug has very low priority.

Probably worth fixing anyway, it may be hiding some other issue?

May I know that is this bug verified?

I tested it with Chrome-stable-66.0.3359.117(64-bit) and Chrome-canary-68.0.3404.0(64bit), but can't reproduce this bug with following steps:
1. enable all "vr/xr" related flags
2. open steam with HTC vive connected
3. open a VR page such as https://webvr.info/samples/03-vr-presentation.html
4. enter VR
5. press "Tab" key on the keyboard for a while, more than 15 seconds

Any missing steps or misunderstanding here to reproduce this bug?

Just tested on 66.0.3359.117 and on 68.0.3406.0 (both 64 bit) and I agree that the issue appears to have been resolved.

Removing Blink>WebVR component and assigning to Blink>WebXR 

Removing Blink>WebVR component and assigning to Blink>WebXR 

Not reproing, appears to be fixed.  Please reactivate or file a new issue if you see similar behavior again.