Make clear interface distinction for things called on device by renderer vs. browser/gvrdelegate |
|||||||
Issue descriptionVRDevice interface contains some things triggered by browser, and some triggered by vrshelldelegate - we should distinguish these with separate interfaces, and try to keep GVR-specific things out of VRDevice.
,
May 24 2018
Continuing that thought - there are methods on VRDeviceBase called by devices, and virtual methods meant for VRDeviceBase to call in response to delegate/browser/renderer calls. If these aren't separated out and well defined, it would make sense to fix that at the same time.
,
Jul 4
,
Jul 4
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
,
Aug 7
Removing Internals>VR component and assigning to Internals>XR
,
Aug 7
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ddorwin@chromium.org
, May 23 2018Labels: XR-Device
Status: Assigned (was: Untriaged)