- From: Rottsches, Dominik <dominik.rottsches@intel.com>
- Date: Thu, 6 Feb 2014 18:49:17 +0000
- To: "public-webscreens@w3.org" <public-webscreens@w3.org>
- CC: Anton Vayvod <avayvod@google.com>
Hi Anton, On 06 Feb 2014, at 12:38, Anton Vayvod <avayvod@google.com<mailto:avayvod@google.com>> wrote: If you connect a �controller" page to a YouTube page in TV mode [1], the paired targets show up in a UI selection, along with the name of the available Chromecast, as shown here: http://roettsch.es/player_target_list.png This server requires a login when I click on the link. However, I think I understand what you mean and thanks for reminding of this important use case. I tested the Cast Chrome extension and YouTube in Chrome with multiple Chromecasts, and they show up as entires with names in the page-embedded YouTube selection dialog (even though the web-based Cast SDK does not allow enumerating them). So, not only proprietary paired devices as in our Youtube.com/tv<http://Youtube.com/tv> example, but also Chromecasts do show up in the YouTube�s page selection UI. If your goal is to cover most Chromecast usage scenarios under Presentation API, it seems to me that name-based enumeration would be required. Dominik
Received on Thursday, 6 February 2014 18:49:47 UTC