Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define user agent context for rendering the presentation #14

Closed
mfoltzgoogle opened this issue Sep 3, 2014 · 3 comments · Fixed by #219
Closed

Define user agent context for rendering the presentation #14

mfoltzgoogle opened this issue Sep 3, 2014 · 3 comments · Fixed by #219

Comments

@mfoltzgoogle
Copy link
Contributor

The spec should specify any restrictions on the presenting browsing context when the opening browsing context is in "incognito" mode.

From public-webscreens and related threads:

The specification should define the behavior of the following Web features for the presenting page across presentation sessions. The goals are the following:

  1. Ensure that the same presentation will behave correctly in the 1-UA and 2-UA cases
  2. Information does not leak from presentation session to session in cases where the controlling pages may represent different authorization domains (e.g., logged-in users).

The following Web features have been discussed (and there may be others to consider):

  • Cookies and local storage
  • Sensor APIs (geo, orientation, etc.)
  • Browser extensions
  • HTTP Cache
  • Shared Workers
@tidoust
Copy link
Member

tidoust commented May 19, 2015

See related discussion and action at Berlin F2F:
http://www.w3.org/2015/05/19-webscreens-minutes.html#item13

@anssiko
Copy link
Member

anssiko commented May 20, 2015

ACTION: @mfoltzgoogle to define browsing context in terms of the upcoming spec for private browsing, perhaps using the Mozilla link as an interim reference. [recorded in http://www.w3.org/2015/05/19-webscreens-minutes.html#action14]

@anssiko anssiko added the action label May 20, 2015
@anssiko
Copy link
Member

anssiko commented May 20, 2015

Should also decide whether the presenting page is able to navigate to another URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants