Move arcore_device out of chrome/browser/android/vr/ |
||||||||
Issue descriptionThe ARCoreDevice implementation and related code are currently in chrome/browser/android/vr/arcore_device/. It should be alongside other XR device runtime implementations - somewhere that will allow non-Chrome embedders, such as WebView to access it.
,
Jun 7 2018
,
Jul 4
,
Jul 11
,
Jul 11
,
Sep 4
The scope of this is not clear - there are lots of dependencies that need to be changed in order for this to work.
,
Sep 4
,
Sep 14
not absolutely required - downgrading to P3
,
Jan 9
,
Jan 18
(4 days ago)
Once this work is complete, enable_arcore should not depend on enable_vr. There is probably some common code (e.g., xr_runtime_manager*) that is required for AR, and we'll need to figure out how to handle that. For example, do we need enable_xr or should we always build the non-platform-specific XR code? |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ddorwin@chromium.org
, May 26 2018