Android Cast SDK can help with the multiple cast urls only (tracking availability for multiple application ids is pretty easy to implement with Cast v2 but choosing which application id to launch is something that will need to be implemented in sync with the component extension's logic if any).

We'd have to implement 1-UA mode to support arbitrary Presentation URLs and we'd need a DIAL backend to implement dial URLs which Android SDK doesn't support (although could if they wanted to).

For now, picking the first cast URL should be a good first step.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f2b47e0f2dfe85e431ec24573651244a9b86af67

commit f2b47e0f2dfe85e431ec24573651244a9b86af67
Author: Anton Vayvod <avayvod@google.com>
Date: Tue Jun 27 20:44:36 2017

[Cast,Android] Pass all the source ids to the MediaRouter dialog manager.

So far the dialog manager picks the first source that it understands and
proceeds with it as the one.

Further work would actually combine all supported sources into a single
MediaRouteSelector to show all compatible devices and later would pick
the right source to pass back to CreateRoute from OnSinkSelected.

BUG= 734639 

Change-Id: I2cbda6f9e11f5c1b46804d68b9951986b55f1b08
Reviewed-on: https://chromium-review.googlesource.com/540415
Commit-Queue: Anton Vayvod <avayvod@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#482738}
[modify] https://crrev.com/f2b47e0f2dfe85e431ec24573651244a9b86af67/chrome/android/java/src/org/chromium/chrome/browser/media/router/ChromeMediaRouterDialogController.java
[modify] https://crrev.com/f2b47e0f2dfe85e431ec24573651244a9b86af67/chrome/android/java/src/org/chromium/chrome/browser/media/router/MediaRouteChooserDialogManager.java
[modify] https://crrev.com/f2b47e0f2dfe85e431ec24573651244a9b86af67/chrome/android/java/src/org/chromium/chrome/browser/media/router/MediaRouteDialogDelegate.java
[modify] https://crrev.com/f2b47e0f2dfe85e431ec24573651244a9b86af67/chrome/browser/media/android/router/media_router_dialog_controller_android.cc
[modify] https://crrev.com/f2b47e0f2dfe85e431ec24573651244a9b86af67/chrome/browser/media/android/router/media_router_dialog_controller_android.h

This should unblock the RemotePlayback API W3C testing.
Some work is remaining to actually check all the Cast URLs, combine all app ids into the discovery selector and then pick the app id to launch based on the requested capabilities for each URL and what the selected sink supports.

s/RemotePlayback/PresentationAPI

 Issue 586690  has been merged into this issue.

The main driver of this feature request (YouTube) won't be needing it soon.  Still worth fixing eventually.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

No current use case for mobile.  Will reactivate if one is conceived.