New issue
Advanced search Search tips

Issue 697160 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocked on:
issue 754101


Participants' hotlists:
media-router-PE


Sign in to add a comment

[Media Router] Dialog doesn't show sink name in the header for DIAL or wired display sinks

Project Member Reported by mfo...@chromium.org, Feb 28 2017

Issue description

Chrome Version: 58

What steps will reproduce the problem?
(1) Cast YouTube to a DIAL-only device (e.g., Samsung TV)
(2) Switch tabs and open MR dialog

What is the expected result?

Dialog shows Samsung TV model name in title

What happens instead?

Title is blank

----
imcheng@:

It's due to a limitation of our MediaRoute data model / media sinks query. The title is populated with the name of the sink, but in this scenario the UI knows about the DIAL route, but not the DIAL sink (since it's not compatible with sources). One fix would be to include sink information with the route itself.
 

Comment 1 by mfo...@chromium.org, Feb 28 2017

Labels: Hotlist-Polish
Status: Available (was: Untriaged)

Comment 3 by sko...@chromium.org, May 10 2017

Labels: Hotlist-Fixit-PE2017
Blockedon: 754101
Cc: dbbrooks@chromium.org
Summary: [Media Router] Dialog doesn't show sink name in the header for DIAL or wired display sinks (was: [Media Router] Always send media sink data with media routes to UI)
This will be resolved by our transition to a native dialog.

Comment 5 by mfo...@chromium.org, Mar 31 2018

Labels: -Hotlist-Fixit-PE2017

Comment 6 by mfo...@chromium.org, Jun 12 2018

Owner: taku...@chromium.org
Status: Assigned (was: Available)
=> takumif to test behavior for DIAL devices, to see if this issue remains with the Harmony dialog.  I believe the new data model for the UI should address the underlying problem here.


Status: WontFix (was: Assigned)
The issue is different for the Harmony dialog. If we have an active session on a DIAL device and open a dialog for a source that's not compatible with DIAL, the device doesn't exist on the list. This was true for the WebUI dialog as well, but now that we don't have a route details view, we cannot stop casting to the DIAL device from a dialog opened on some other tab.
Status: Assigned (was: WontFix)
Logged new issue for #7: bug 872061
Cc: -imch...@chromium.org

Sign in to add a comment