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

CHIPS (Cookies Having Independent Partitioned State) #678

Closed
johannhof opened this issue Aug 25, 2022 · 4 comments · Fixed by #682
Closed

CHIPS (Cookies Having Independent Partitioned State) #678

johannhof opened this issue Aug 25, 2022 · 4 comments · Fixed by #682

Comments

@johannhof
Copy link

Request for Mozilla Position on an Emerging Web Specification

Other information

CHIPS is a proposal for a new cookie attribute, Partitioned. This attribute will indicate to user agents that these cross-site cookies should only be available in the same top-level context that the cookie was first set in.

CHIPS has been discussed in PrivacyCG and beyond for a while, and participants from other browsers including Firefox have generally signaled support so far (with a few details to figure out), see privacycg/proposals#30.

The TAG Review reached an overall positive conclusion

@johannhof
Copy link
Author

cc @DCtheTall @krgovind

@johannhof
Copy link
Author

WebKit position issue: WebKit/standards-positions#50

@bvandersloot-mozilla
Copy link
Contributor

We are going to mark this as "positive" via #682.

A key piece of this decision is the behavior of a cookie when the Partitioned attribute is not provided being left up to the implementer. This allows us to continue deployment of partitioning by default while not forcing other browsers to change their default cookie behavior immediately.

@johannhof
Copy link
Author

Great, thank you for the update, @bvandersloot-mozilla! I agree that we should preserve this condition for browsers.

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.

3 participants