- From: Bassbouss, Louay <louay.bassbouss@fokus.fraunhofer.de>
- Date: Tue, 11 Nov 2014 14:50:44 +0000
- To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "public-secondscreen@w3.org" <public-secondscreen@w3.org>, "public-webscreens@w3.org" <public-webscreens@w3.org>, "mark a. foltz" <mfoltz@google.com>
Hi MarkFo, Anssi, All, If I understand correctly, we need to extend the spec to let the origin page receive the session created by the Browser? Another question, how the origin page can pass a session id to join an existing session? Louay > -----Original Message----- > From: Kostiainen, Anssi [mailto:anssi.kostiainen@intel.com] > Sent: Dienstag, 11. November 2014 15:29 > To: public-secondscreen@w3.org; public-webscreens@w3.org; mark a. foltz > Subject: Allow page to designate a default presentation URL > > Hi MarkFo, All, > > MarkFo suggested [1] the following feature to the Presentation API I'd like to > bring to the mailing list for further discussion: > > [[ > > Allow page to designate a default presentation URL > > Some user agents may wish to allow the user to initiate presentation from > the browser instead of by triggering it via an action on the page. This is > analogous to choosing "Print" from the browser menu instead of calling > window.print(). > > In this scenario, the page should be able to designate a default presentation > URL that will be shown when the user initiates presentation via the browser. > > [...] > > ]] > > Here's how I (puts hat off) see this could work: > > * The page at https://example.org/ defines its default presentation URL by > providing a hint to the UA, for example: > > <link rel="presentation" href="show.html"> > > * The user initiates the presentation from the UA's user interface (e.g. > chooses File > Present, taps a dedicated button -- an implementation detail). > > * The UA behaves as if startSession("https://example.org/show.html") was > invoked. > That's omitting a lot of details, for example, how this ties into the event > lifecycle. > > In addition to the print use case MarkFo mentions above, this is similar to the > way how the W3C Manifest spec [2] enables the "add to homescreen" flow. > > [hat on] > > All - please let us know if you have comments or feedback on the proposal. > > MarkFo - what is the relationship between [1] and [3]? > > Thanks, > > -Anssi > > [1] https://github.com/w3c/presentation-api/issues/26 > [2] http://w3c.github.io/manifest/ > [3] http://lists.w3.org/Archives/Public/public- > webscreens/2014Sep/0039.html
Received on Tuesday, 11 November 2014 14:51:21 UTC