- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Feb 2015 19:07:56 +0000
- To: public-secondscreen@w3.org
mfoltzgoogle has just created a new issue for https://github.com/w3c/presentation-api: == Add facility for the opening page to add cloud paired screens as presentation targets == The assumption thus far is that the user agent is the only entity that can determine what screens are available for presentation. However, some sites will be able to access screens entirely based on interaction over the Internet, i.e. using XHR or WebSockets to a server, or perhaps WebRTC. Ideally these should be offered to the user as presentation targets alongside browser-discovered screens, so that the site author doesn't have to offer two distinct presentation mechanisms. Considerations: * The browser would only be responsible for offering the screen as a choice, and informing the app that it was chosen for presentation. It would not be responsible for any further interaction. * These screens would need to be clearly and distinctly labeled as belonging to the site, and not part of the automatic discovery process by the browser. I think this is a useful enhancement that would allow innovation and extension over browser-provided presentation capabilities. See https://github.com/w3c/presentation-api/issues/61
Received on Wednesday, 25 February 2015 19:09:02 UTC