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

Issue 670129 link

Starred by 3 users
Status: Duplicate
Owner:
█ ymalik@chromium.org
(currently inactive on Chromium)
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Feature
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

VR: Handle incoming intents

Project Member Reported by ddorwin@chromium.org, Dec 1 2016 
Handle appropriate intents so other Daydream apps can launch Chrome as appropriate.

Comment 1 by ddorwin@chromium.org, Dec 1 2016 

Issue 641465 has been merged into this issue.

Comment 2 by bshe@chromium.org, Dec 15 2016 

Note it may result a regular 2D page displayed in WebVR mode in some scenarios on such Intent. It should be displayed in ChromeVr mode. See: https://bugs.chromium.org/p/chromium/issues/detail?id=673019

The main reason is that a WebVR page may listening a vrdisplayactivate event before the new requested page open. In such case, the event is dispatched and the WebVR
page then triggers WebVr mode.

Comment 3 by ddorwin@chromium.org, Nov 6 2017

Owner: ymalik@chromium.org
Status: Assigned (was: Available)
ymalik: Is this a duplicate of another issue?

Comment 4 by ymalik@chromium.org, Nov 7 2017

Mergedinto: 752200
Status: Duplicate (was: Assigned)
Yes, merged into the umbrella bug.
►

Sign in to add a comment