- From: Rottsches, Dominik <dominik.rottsches@intel.com>
- Date: Fri, 16 May 2014 07:22:22 +0000
- To: Mark Watson <watsonm@netflix.com>
- CC: "public-webscreens@w3.org" <public-webscreens@w3.org>, "mark a. foltz" <mfoltz@google.com>
Hi MarkW,
> In "API and associated specification", where we say "An API to allow a web application to request display of web content on a connected display, with a means to communicate with and control the web content from the initiating page and other authorized pages", I think we should explicitly add something like "and a means to discover when a display capable of rendering the web content is available".
>
> This is the major requirement that is not presently supported by the API draft: there is no way at present for the web page to determine whether it should render the icon that shows the user a capable display is available (and we have decided it should be the page that renders that icon, not the UA).
Note that the API draft [1] supports this:
presentation.onavailablechange = function(e) {
showButton.disabled = !e.available;
showButton.onclick = show;
};
I agree that we should add the sentence you’re suggesting. We should then incorporate the availability information concept into the use cases section of the API discussion as well.
Dominik
[1] https://www.w3.org/community/webscreens/wiki/API_Discussion
Received on Friday, 16 May 2014 07:32:28 UTC