Chrome Version       : 69.0.3475.0 (Official Build) dev (32-bit)
URLs (if applicable) : N/A
Other browsers tested: N/A

What steps will reproduce the problem?
(1) open chrome://flags and set #webxr to enabled and #webxr-hit-test to default/disabled.
(2) relaunch Chrome
(3) open any page that uses the WebXR API (without the Hit Test API)

What is the expected result?
The camera stream should be turned on in the background, ARCore 6DOF tracking should start working and the WebXR app should work as expected.

What happens instead?
The camera stream is never turned on and this means ARCore 6DOF tracking never starts - so the WebXR app just acts like a VR app instead (e.g. 3DOF orientation only tracking). If you go back into chrome://flags and set #webxr-hit-test to enabled then the app goes back to working as expected.

Please provide any additional information below. Attach a screenshot if
possible.
The Hit Test API is very useful - but this silent dependency means that we can't deploy WebXR using our Origin Trial token without still requiring the user to manually enable the #webxr-hit-test flag.

Can we please either automatically enable the #webxr-hit-test capability if #webxr is enabled - or separate the silent dependency so #webxr can at least work on it's own.

NOTE: The Origin Trial team recommended we raise this ticket - also see our initial comment here: https://bugs.chromium.org/p/chromium/issues/detail?id=833633#c11


BTW: Thanks for all the great progress on these APIs 8)