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

Issue 738196 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
ddorwin@chromium.org
█ asimjour@chromium.org
mfo...@chromium.org
btolsch@chromium.org
powerb@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug
Proj-XR
Proj-XR-VR


Participants' hotlists:
media-router-follow-up


Sign in to add a comment

[VrShell] Mark media router screens as unavailable in VR

Project Member Reported by amp@chromium.org, Jun 29 2017 
Currently (as of https://chromium-review.googlesource.com/549516) the media router dialog is suppresed when in VR.

This leads to a less than ideal experience as the user can still see a cast icon in VR, but it appears non-functional.  Also any existing cast sessions would become uncontrollable.

Until a working Media Router dialog is available (see  issue 736568 ) we should mark screens as unavailable when entering VR (and the inverse when leaving VR) so that the icon doesn't appear at all.

The desired experience with regards to existing sessions should be defined (ie do we let the session continue even though it is no longer controllable, or should we kill the session?).

Comment 1 by mfo...@chromium.org, Jun 29 2017

Components: -Internals>Cast>API Blink>PresentationAPI
Thanks.

For either the Presentation API or Remote Playback API, the remote experience should be controllable through the content area as long as the page that started it is interactive through VR.

For Remote Playback, if the original page is closed or put in the background then it's a question of how to surface the media controls notification.  Maybe that should be considered separately from addressing the API behavior.

Comment 2 by ddorwin@chromium.org, Jul 14 2017

Status: Available (was: Untriaged)

Comment 3 by mfo...@chromium.org, Apr 5 2018

Labels: Needs-Feedback
amp@: Can you confirm that this is a P3 for the VR experience (i.e. fine as a backlog item)?

Comment 4 by amp@chromium.org, Apr 6 2018

Cc: ddorwin@chromium.org
ddorwin@, is there a vr backlog that we should add this to and figure out relative priority?

Comment 5 by asimjour@chromium.org, Jun 5 2018

Owner: asimjour@chromium.org
Status: Assigned (was: Available)

Comment 6 by mthiesse@chromium.org, Jun 26 2018

Labels: VRB-Next-Triage

Comment 7 by asimjour@chromium.org, Aug 27

Cc: asimjour@chromium.org
Owner: ----
Status: Available (was: Assigned)

Comment 8 by elalish@google.com, Today (3 hours ago) 

Does anyone have repro steps for this?
►

Sign in to add a comment