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

Issue 695934 link

Starred by 3 users
Status: Verified
Owner: ----
Closed: Oct 2017
Cc:
vsupruniuk@google.com
█ leilei@chromium.org
█ meganlindsay@chromium.org
mthiesse@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-VR
Proj-XR



Sign in to add a comment

Inserting device into headset fails to load daydream app

Project Member Reported by dbbrooks@chromium.org, Feb 24 2017 
Chrome Version: 57.0.2987.77
OS: Android 7.1.2 Pixel XL

What steps will reproduce the problem?
Setup: Daydream app installed, set up, and set to default viewer.

(1) Go to vr.with.in
(2) Insert device into daydream headset without pressing the enter vr button
(3) press the controller button when prompted to sync it.

What is the expected result? One of two things: 1. The site supports autodetect and enters VR mode. 2. The site doesn't support autodetect and the daydream app homescreen is displayed.

What happens instead? The vr.with.in site is displayed but not in VR mode. 

Assuming this site doesn't support autodetect, I'm curious why the daydream app's homescreen in VR mode isn't opened in this case. It is when these steps are followed from other sites.

Comment 1 by bsheedy@chromium.org, Feb 24 2017 

Pretty sure this is an issue with the site itself, not something on our end.

AFAIK, we don't go to Daydream Home if the page has a listener for 'vrdisplayactivate', as normally you would listen for that then call requestPresent() in response.

Looking at the Javascript for the page (https://vr.with.in/build/within-vr-menu.js), they do have a vrdisplayactivate listener, but aren't requesting presentation with it.

Comment 2 by mthiesse@chromium.org, Feb 24 2017

Labels: -Pri-3 Pri-2
That's exactly right. We should improve the UX though in cases where the page doesn't actually call requestPresent.

Comment 3 by ddorwin@chromium.org, Feb 27 2017

Cc: meganlindsay@chromium.org
mthiesse: Are you suggesting we do something if the site has used WebVR in some way but does not present? I'm not sure what we'd do.

meganlindsay: This specific case might need outreach.

Comment 4 by mthiesse@chromium.org, Feb 27 2017 

Well we can detect when vrdisplayactivate fires, but requestPresent isn't called in response, and we can return to daydream home, or do something else.

Comment 5 by j...@with.in, Feb 27 2017 

We'll get on this to make sure that we're listening to that specific event on the Within site. Thanks for reporting!

Comment 6 by bsheedy@chromium.org, Mar 2 2017

Status: ExternalDependency (was: Untriaged)

Comment 7 by cjgrant@chromium.org, Oct 10 2017

Cc: mthiesse@chromium.org
Status: Fixed (was: ExternalDependency)
I tried to repro this, and vr.with.in appears to work fine now - the site enters WebVR on headset detection.

jono@with.in, it looks like you're now listening to that specific event.

dbbrooks@, I'll close this off.  Please re-open/object if I've missed something.

mthiesse@, we should have a separate bug to pursue better UX, if we still think this would help.

Comment 8 by vsupruniuk@google.com, Oct 27 2017

Status: Verified (was: Fixed)
Verified in Chrome Dev 64.0.3249.0

Comment 9 by btebbs@chromium.org, Jul 4

Components: Blink>WebXR
►

Sign in to add a comment