W3C home > Mailing lists > Public > public-secondscreen@w3.org > November 2016

[presentation-api] Well defined environment for nested contexts of the receiving browsing context?

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Wed, 16 Nov 2016 10:24:50 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-189658197-1479291889-sysbot+gh@w3.org>
tidoust has just created a new issue for 
https://github.com/w3c/presentation-api:

== Well defined environment for nested contexts of the receiving 
browsing context? ==
The Presentation API imposes a well-defined environment for the 
[receiving browsing 
context](https://w3c.github.io/presentation-api/#creating-a-receiving-browsing-context)
 when it is created, but it does not say anything about nested 
browsing contexts that this browsing context could create (e.g. with 
an `<iframe>`).

I'm not clear how the restrictions on cookies, Application cache, 
Permissions, IndexedDB, Web Storage, and Service Workers propagate to 
nested browsing contexts in particular. Should the spec rather attach 
the steps that deal with these constraints to the [create a browsing 
context](http://w3c.github.io/html/browsers.html#creating-a-new-browsing-context)
 algorithm in HTML so that they apply to all browsing contexts on the 
receiving side?

(This issue is unrelated to but still triggered by the discussion 
around `[SameObject]` and receiving browsing contexts in #365)



Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/367 using your GitHub 
account
Received on Wednesday, 16 November 2016 10:24:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 16 November 2016 10:24:57 UTC