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

Issue 803487 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
█ vollick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-XR



Sign in to add a comment

☂ Avoid doing VR-browsing-only work when VR Browsing won't be used.

Project Member Reported by mthiesse@chromium.org, Jan 18 2018 
We do a few things like creating unnecessary surfaces and textures when we know that VR browsing isn't going to be used during a VR session. We should probably not do that.

Comment 1 by ddorwin@chromium.org, Jan 18 2018 

Never at build time or runtime? For the former,  issue 731802  may be related.

Comment 2 by mthiesse@chromium.org, Jan 19 2018

Description: Show this description

Comment 3 by mthiesse@chromium.org, Jan 19 2018

Summary: ☂ Avoid doing VR-browsing-only work when VR Browsing won't be used. (was: ☂ Avoid doing VR-browsing-only work when VR Browsing is disabled.)
Clarified. This bug captures work that we can't compile out/put behind a flag, but depends on things like the VR headset being used, or the type of ChromeActivity being used for VR.

Comment 4 by mthiesse@chromium.org, Jun 27 2018

Labels: VRB-Next-Triage

Comment 5 by btebbs@chromium.org, Jul 4

Components: Internals>XR

Comment 6 by efoo@chromium.org, Aug 7 

Removing Internals>VR component and assigning to Internals>XR

Comment 7 by efoo@chromium.org, Aug 7

Components: -Internals>VR
►

Sign in to add a comment