Hi, Colin and bajones@, 

Colin commented that "there is a tentative plan to eliminate VR's dependence on Gamepad, but the timeframe is not clear" in Dec.

May I ask what the current status? Because my colleague Donna is very interested to do something in VR. So is there anything we can help? Thank you:)

bajones@/mthiesse@, am I correct in assuming that nothing has concretely changed here at this point? i.e. the VR impl is still dependent on the gamepad impl in Chromium.

Thanks!

Nothing has concretely changed yet, and probably won't until we unship WebVR 1.1.

Brandon can correct me if I'm wrong here, but it looks like WebXR will not be using the gamepad to expose VR controllers? So when that fully replaces WebVR we should be able to eliminate the gamepad dependence.

mthiesse@ is correct, we don't have plans to make use of the Gamepad API in WebXR at this point. We're taking a very conservative approach to input for the first pass at the API. In the future we may extend our input story to expose more detailed controller information, and that may make use of Gamepad again, but nobody is looking at that yet.

Thanks! Looks like there's nothing applicable here at this point. Donna, as we wind down work on MTP we'll be able to find something else of interest in the Device Service I'm sure.

Thank you all for the information.
Brandon@, mthiesse@ please correct me if I'm wrong with following understandings.

WebVR 1.1 implementation will be removed from chromium when WebXR is ready and relatively stable with the simple version input implementation(https://github.com/immersive-web/webxr/pull/325).
As the simple-version input would not depend on Gamepad, this issue(774363) can be marked as fixed.
Then Gamepad servicification work can be finished. In the future, WebXR may still need to depend to Gamepad service for complicated input features.

And I have some questions here:
1. Do we have plans or estimated time for WebVR 1.1 unshiping? As I know that WebXR API bindings are still using the same underline VR service and infrastructure code with WebVR, will these underline code be refactored in the near future?
2. What the key problems if we try to finish Gamepad servicification with VR dependency? A problem I can see:
   various VR devices need to expose their input capabilities by implementing GamepadDataFetcher, so that will be a hard depend which can not be divided in to two different services.
   Is this the key problem, or others?

Thank you very much, Colin@! That't great and I appreciate your help.

Removing Blink>WebVR component and assigning to Blink>WebXR 

Removing Blink>WebVR component and assigning to Blink>WebXR