Implement Cookie-Store API
Categories
(Core :: DOM: Core & HTML, enhancement, P5)
Tracking
()
People
(Reporter: baku, Unassigned)
References
()
Details
(Keywords: dev-doc-needed, parity-chrome, parity-safari)
Attachments
(1 file, 1 obsolete file)
|
106.26 KB,
patch
|
Details | Diff | Splinter Review |
An asynchronous Javascript cookies API for documents and workers
|
Reporter | |
Comment 1•6 years ago
|
||
This is just a proof of concept. It works, but many details are missing: . the API is not exposed to workers . not all the WPTs pass I don't have time to work on this, but if somebody wants to continue the development, this patch is a good starting point. I can also help or be mentor.
|
|
Reporter | |
Comment 2•6 years ago
|
||
|
||
Updated•6 years ago
|
|
Assignee | |
Updated•5 years ago
|
Blink intent to ship: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/zOsGZGMGiM4/zdJGMq5iBwAJ
|
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 4•3 years ago
|
||
Any eta on this?
|
||
Comment 5•3 years ago
|
||
It would be great if this could be implemented in Firefox. The API is much nicer to work with than document.cookie, and would allow many developers to remove third party dependencies that they use purely for nice cookie management.
|
||
Updated•2 years ago
|
|
||
Updated•2 years ago
|
|
||
Updated•2 years ago
|
|
||
Comment 6•8 months ago
|
||
It looks like Safari is now implementing this API.
|
||
Comment 7•3 months ago
|
||
FWIW, having an async, far cleaner API for cookies is nice DX and may benefit performance, but I think it's worth calling out that one of the key additions is the "Monitoring Cookies" feature.
In order to achieve this in a polyfill—as per Keith Cirkel's comment—involves using postMessage and BroadcastChannel, which could conflict with other uses of those APIs and would add significant weight to the polyfill.
I'm not suggesting the Monitoring Cookies feature should be implemented in lieu of the rest of the API, I'm just trying to add weight to the need for the overall Cookie Store API to be implemented given that feature is a significant challenge to polyfill.
WebKit appear to have made significant progress on their implementation now, only one bug is outstanding: https://bugs.webkit.org/show_bug.cgi?id=258504 so if this make a Safari release shortly, this would leave Firefox being the only browser without support.
|
|
||
Updated•2 months ago
|
Description
•