New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 839253 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Task
Proj-VR
Proj-XR



Sign in to add a comment

Support VRDisplay.can_provide_pass_through_images for exclusive mode

Project Member Reported by lincolnfrog@google.com, May 3 2018

Issue description

Currently only magic-window AR is supported. We should generalize the code that renders camera frames as part of the magic window AR code path (that calls device->xrMagicWindowProviderPtr()->GetFrameData(...)). This behavior is needed in exclusive frame generation path as well.
 
Labels: Pri-3 Type-Task
Status: Available (was: Unconfirmed)
Cc: offenwanger@chromium.org billorr@chromium.org
Labels: XR-Device
Owner: lincolnfrog@chromium.org
Status: Assigned (was: Available)
You might want to wait until some of the refactoring settles down before attempting to address this.
Components: Blink>WebXR
Components: -Blink>WebXR Blink>WebXR>AR
Labels: BlinkWebXR
Removing Blink>WebVR component and assigning to Blink>WebXR 
Components: Blink>WebXR
Labels: -BlinkWebXR
Removing Blink>WebVR component and assigning to Blink>WebXR 
Components: -Blink>WebVR
Labels: AR-Rendering
Labels: -Pri-3 Pri-2
Things could change a lot here with the new XR Modes proposal. I'd wait until we're ready to implement that before doing more work on various modes.
Cc: lincolnfrog@chromium.org
Owner: klausw@chromium.org

Sign in to add a comment