- From: Mark Watson <watsonm@netflix.com>
- Date: Mon, 10 Mar 2014 09:24:45 -0700
- To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
- Cc: "public-webscreens@w3.org" <public-webscreens@w3.org>
- Message-ID: <CAEnTvdDt5rL_dogsBTt9nZFZZqT7T5+rOP6A7MVFobsbx2o48A@mail.gmail.com>
Hi Anssi, I don't quite follow how this API works for the flinging case. First, I understand now why we would like the site to render the button that pops up the device list (because it may want to show several, for different things to be potentially sent to different screens). The first thing that should happen, then, is that the site informs the UA of the URL(s) it might wish to present. This tells the UA to start the discovery processes (if not always running) and what kind of URL support to look for. For example, if the site wants to show content from www.netflix.com and all that can be found through the various discovery mechanisms is a www.youtube.com application advertised over DIAL, then there are no screens available that the site can use and the icon should not be shown at all. With the API as documented, though, IIUC, the first thing that happens is that the site gets the onavailablechange event. How can the browser generate this without knowing the URL ? Second, the site ought to be able to cause the UA-managed selection list to appear at a position of its choice, for example close to the icon that triggered the list to be shown. It seems also that if there are multiple second-screen buttons then a URL is needed for each and the device list may be different for each. This would suggest to me that the availablechange event should be on the PresentationSession, which then means that much more than one bit of information is being revealed to the site. ...Mark On Mon, Mar 3, 2014 at 7:46 AM, Kostiainen, Anssi < anssi.kostiainen@intel.com> wrote: > Hi All, > > As a group, we've now mulled over the design of the revised Presentation > API by looking at the use cases, requirements, and concrete usage examples. > > As the concrete next step, we've drafted the WebIDL for the updated > Presentation API, ready for your review at: > > https://www.w3.org/community/webscreens/wiki/API_Discussion#WebIDL > > All - please review the WebIDL and chime in on the list if you have any > questions or concerns, big or small. Also, if you're happy with the > direction, positive signals are also encouraged, even if just +1s. As > usual, silence is considered consent. > > Before we start land changes to the spec itself, we want to ensure we're > aligned, so your feedback at this stage is much appreciated. > > Thanks, > > -Anssi > >
Received on Monday, 10 March 2014 16:25:14 UTC