generated from privacycg/template
-
Notifications
You must be signed in to change notification settings - Fork 9
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
What state should be able to have its keying relaxed? #7
Comments
I think this is leaning toward storage + cookies, but properly formalizing that is still work in progress. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue ties into the Storage Access API, but is also relevant here as it has implications for the architecture of the affected pieces of state.
Firefox has an implementation where Cookies and all of Storage go between having additional keying and not having additional keying depending on the Storage Access API.
Safari allows Cookies to go between blocked and not having additional keying (i.e., first-party access).
I'm not aware what Chrome is planning here.
The text was updated successfully, but these errors were encountered: