Enable WebVR origin trial experiments.

content/browser/frame_host/render_frame_host_impl.cc

Index: content/browser/frame_host/render_frame_host_impl.cc
diff --git a/content/browser/frame_host/render_frame_host_impl.cc b/content/browser/frame_host/render_frame_host_impl.cc
index 759b8b3368f566ac400ab68d916c9c68f83c9eb4..5530e82ff19d97e22ff6f14744fdb51702fb5f59 100644
--- a/content/browser/frame_host/render_frame_host_impl.cc
+++ b/content/browser/frame_host/render_frame_host_impl.cc
@@ -2184,7 +2184,16 @@ void RenderFrameHostImpl::RegisterMojoInterfaces() {
   const base::CommandLine& browser_command_line =
       *base::CommandLine::ForCurrentProcess();
 
+  // What to do here?  This is behind a build flag any way so maybe wait until

[iclelland, 2016/10/05 21:55:57]

If WebVR ships as an origin trial, then I think that you'll need to enable the
browser-side components unconditionally, since you can't tell whether any given
renderer is going to need it until it actually navigates to the page.

[amp, 2016/10/05 22:04:43]

I think we are going for having the components always there, but I'm not exactly
sure what the VRService here does so I'll dig a bit more.

+  // that is fixed to modify this, but then should this be gated by runtime and
+  // origin trial features, not a command line switch directly?
+  // WebBluetooth (which is also in an origin trial) also uses a command line
+  // switch in this file.
   if (browser_command_line.HasSwitch(switches::kEnableWebVR)) {
+  /*
+  if (RuntimeEnabledFeatures::webVREnabled())
+    // || OriginTrials::webVREnabled())
+  */
     GetInterfaceRegistry()->AddInterface<device::VRService>(
         base::Bind(&device::VRServiceImpl::BindRequest));
   }