258504 2023-06-25 15:38:19 -0700 [Meta] Implement the cookie-store API 2024-09-13 13:27:55 -0700 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified NEW https://wicg.github.io/cookie-store/#CookieStore InRadar P2 Normal --- 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 1 cdumez rupin agafvv lwarlow rik rjesup ryan webkit-bug-importer oldest_to_newest 1963525 0 cdumez 2023-06-25 15:38:19 -0700 Implement the cookie-store API behind an experimental feature flag: - https://wicg.github.io/cookie-store/#CookieStore 1964703 1 webkit-bug-importer 2023-07-02 15:39:14 -0700 <rdar://problem/111656826> 1964955 2 rik 2023-07-04 02:40:01 -0700 I believe bug 258651 is part of this effort. 1965128 3 cdumez 2023-07-05 08:43:12 -0700 (In reply to Anthony Ricaud from comment #2) > I believe bug 258651 is part of this effort. Indeed, thanks. 1967440 4 lwarlow 2023-07-20 02:29:44 -0700 *** Bug 231750 has been marked as a duplicate of this bug. *** 2043168 5 rjesup 2024-06-26 05:55:58 -0700 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! 2043243 6 rjesup 2024-06-26 13:01:10 -0700 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 2051660 7 cdumez 2024-08-09 08:39:26 -0700 (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.