Bug 258504
| Summary: | [Meta] Implement the cookie-store API | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Chris Dumez <cdumez> |
| Component: | WebCore Misc. | Assignee: | rupin |
| Status: | NEW | ||
| Severity: | Normal | CC: | agafvv, lwarlow, rik, rjesup, ryan, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://wicg.github.io/cookie-store/#CookieStore | ||
| Bug Depends on: | 259341, 258503, 258651, 259071, 259126, 259196, 259220, 259295, 259340, 259505, 259529, 259571, 259710, 259932, 260028, 260103, 260495, 260737, 277781, 277892, 278198, 278245, 279151, 279230, 279454, 279573, 279578, 279688 | ||
| Bug Blocks: | |||
Chris Dumez
Implement the cookie-store API behind an experimental feature flag:
- https://wicg.github.io/cookie-store/#CookieStore
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/111656826>
Anthony Ricaud
I believe bug 258651 is part of this effort.
Chris Dumez
(In reply to Anthony Ricaud from comment #2)
> I believe bug 258651 is part of this effort.
Indeed, thanks.
Luke Warlow
*** Bug 231750 has been marked as a duplicate of this bug. ***
Randell Jesup
What's the status of this work? We at Mozilla had heard that Safari was implementing a subset of the proposed Cookie Store API spec; if so can you indicate what subset you're looking at? Hopefully this deal with the issues we raised in https://github.com/mozilla/standards-positions/issues/94#issuecomment-496973698
Thanks!
Randell Jesup
After some side discussions, Mozilla is going to look to implement a subset of the proposed API, only including whatever is already is exposed by document.cookie, which should address our concerns (and Apple's concerns) with the current proposal; I believe this matches what Anne said in https://github.com/WebKit/standards-positions/issues/36#issuecomment-1620515474
Chris Dumez
(In reply to Randell Jesup from comment #6)
> After some side discussions, Mozilla is going to look to implement a subset
> of the proposed API, only including whatever is already is exposed by
> document.cookie, which should address our concerns (and Apple's concerns)
> with the current proposal; I believe this matches what Anne said in
> https://github.com/WebKit/standards-positions/issues/36#issuecomment-
> 1620515474
We're resuming work on this (Rupin Mittal is now actively working on this).
Our plan is also to only expose properties that were previously accessible via document.cookie.
Please feel free to get in touch with me and Rupin if needed.