Add an ENABLE_VR_BROWSER flag to differentiate platforms that want ENABLE_VR but not yet VR browsing |
|||||||||||||
Issue descriptionThere are some places that ENABLE_VR is used but assumes Android or VR browsing. We should differentiate so we can start supporting Windows without requiring browsing.
,
Jul 7 2017
While low priority, it would be good to get this done before branch cut in order to avoid any merge issues.
,
Jul 7 2017
,
Jul 26 2017
,
Aug 10 2017
,
Oct 12 2017
,
Oct 12 2017
,
Nov 15 2017
I have a start at this.
,
Dec 4 2017
,
Feb 26 2018
,
Jul 4
,
Aug 7
Removing Internals>VR component and remapping to Internals>XR
,
Aug 7
,
Dec 10
At this point, we have most code shared in a common location, and it is used cross platform. I think we can resolve this as "won't fix", but should clean up a todo in chrome_features.h. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by ddorwin@chromium.org
, Jun 9 2017Labels: M-61
Status: Assigned (was: Untriaged)