New issue
Advanced search Search tips

Issue 663922 link

Starred by 3 users
Status: Archived
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Feature
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Improve load times for VR Shell UI contents

Project Member Reported by mthiesse@chromium.org, Nov 9 2016 
Clank supports pre-rendering and swapping in of webcontents for things like omnibar contents you're likely to navigate to.

We should look into doing the same for the VR Shell UI and improving initial startup time.

A possible heuristic for doing the pre-rendering is the user is viewing a WebVR page and Daydream tells us they have a View headset.

Comment 1 by mthiesse@chromium.org, Feb 3 2017

Labels: -Pri-3 VR-DF Pri-2
Summary: Improve load times for VR Shell UI contents (was: Pre-render VR Shell UI contents)
Bumping this up to dogfood.

Some suggestions:
1. Delay loading of content page until UI has loaded (should have huge wins as the UI is really lightweight, but might get starved when loading cnn.com, for example, in the content window)
2. Pause the VR render loop (including webVR) until the UI has loaded.
3. Pre-load UI contents when on WebVR pages and the user is known to use VR.

Comment 2 by cjgrant@chromium.org, Aug 9 2017

Labels: -VR-DF VR-Triage-Close

Comment 3 by cjgrant@chromium.org, Aug 11 2017

Status: Archived (was: Available)
Closing this bug via bulk-edit.  This bug tracks future work that is not yet scoped.  For maintainability, we are now tracking aspirational future work here:

http://go/chrome-vr-backlog

In the future, this bug may be re-opened when in scope, or replaced by a new bug if warranted.
►

Sign in to add a comment