Skip to content

Implement CookieStore API #37674

Open
Open

Description

@sebsebmc

With the release of Firefox 140 all the major browsers now implement the Cookie Store API. I'd like to implement the API and will be using this issue to track the implementation process

Steps:

Activity

  1. added
    B-metaThis issue tracks the status of multiple, related pieces of work
    B-feature-trackingThis issue tracks a particular high-level feature
    and removed
    B-metaThis issue tracks the status of multiple, related pieces of work
    on Jun 24, 2025
  2. arihant2math commented on Jul 31, 2025

    @arihant2math
    Contributor
  3. sebsebmc commented on Jul 31, 2025

    @sebsebmc
    ContributorAuthor

    Yeah and annoyingly they renamed the WPT tests folder as well from cookie-store to cookiestore

  4. TimvdLippe commented on Dec 23, 2025

    @TimvdLippe
    Contributor

    @sebsebmc are you still interested in contributing this web feature? I don't see any open PRs for it and am not sure what the status is. If you are no longer interested, we can find somebody else to work on it as well. I might be able to if that helps.

  5. sebsebmc commented on Dec 23, 2025

    @sebsebmc
    ContributorAuthor

    Sorry about the lack of updates, life has kept me busy. If I remember correctly, the main blocker I was running into was that some of the cookie store tests were testing for nameless cookies, which because of the cookie libraries we use resulted in errors that would time out the test runner.

    I investigated potentially transforming those cookies but ended up finding that there is discussion amongst the spec writers over removing nameless cookies or switching their representation. httpwg/http-extensions#2229

    Hopefully, I should have some time to work on this again in the new year, though any ideas for dealing with nameless cookies in the interim would be great

  6. sebsebmc commented on Dec 23, 2025

    @sebsebmc
    ContributorAuthor

    It definitely feels like something where some strategic amount of non-compliance may be necessary to make forward progress

  7. TimvdLippe commented on Dec 25, 2025

    @TimvdLippe
    Contributor

    I think it's fine to continue implementation as much as we can while the specification settles. Seems like a minor part of the API to me.

  8. skyz1 commented on Oct 29, 2026

    @skyz1
    Contributor

    I will work on the change event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions