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
Cookie Store API #36
Comments
There is also a TAG review request here: w3ctag/design-reviews#290 |
This comment by Ehsan on the Mozilla issue still seems applicable and relevant:
Based on that I'm adding |
Marking this as |
Is https://bugs.webkit.org/show_bug.cgi?id=258504 an indication that WebKit's position has changed? |
I don’t know if we’ve had a chance to communicate our latest analysis but it’s important for us that no cookie metadata is exposed through this API. The old document.cookie API provides key+value and that’s the only thing that should be exposed. User agents should be at liberty to honor, change, or not honor cookie directives, and webpages should not be able to check which decision the user agent made. This is important to be able to protect the user and enforce a cookie policy without websites pushing users to change settings. |
Yeah, couple of things to add to what John said above:
It would be interesting to know if @inexorabletash, @ayuishii, et al. could see eventual convergence on this set of ideas so we might all end up with the same API. |
Modulo compatibility with deployed content, converging on the above seems reasonable. Usage of the API per https://chromestatus.com/metrics/feature/timeline/popularity/2510 is higher than I would have expected, so research (as you're doing) would be necessary to ensure a subset of what Chrome currently ships is feasible. |
The release notes for 17.2 say "Added the change event for the Cookie Store API. (113809948)" It would be good to get some clarity on what parts of the API are supported. https://developer.apple.com/documentation/safari-release-notes/safari-17_2-release-notes |
Given that the API is still behind a "testable" flag, I have a feeling the mention in the 17.2 release notes is a mistake and should be removed. |
Request for position on an emerging web specification
Information about the spec
Design reviews and vendor positions
The text was updated successfully, but these errors were encountered: