Hello TAG!

I'm requesting a TAG review of Cookie Store API.

Cookie Store API offers an asynchronous alternative to document.cookie, and exposes HTTP cookies to service workers. This allows sites to react to cookie changes, such as session cookie changes during authentication, and update the current page UI in response. It also allows service workers to react to these changes and could initiate a cleanup of private cached data.

• Explainer¹: https://github.com/WICG/cookie-store/blob/master/explainer.md
• Specification URL: https://wicg.github.io/cookie-store/
• Tests: WPT
• Security and Privacy self-review²: https://github.com/WICG/cookie-store/blob/master/security-privacy-self-assessment.md
• GitHub repo (if you prefer feedback filed there): https://github.com/WICG/cookie-store
• Primary contacts (and their relationship to the specification):
  • Ayu Ishii (@ayuishii), Google, implementer
  • Victor Costan (@pwnall), Google, specifier/implementer
• Organization(s)/project(s) driving the specification: Chromium
• Key pieces of existing multi-stakeholder review or discussion of this specification:
  • WICG discourse thread
  • TPAC 2017 - WebPlat
  • TPAC 2018 - WebPlat
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5658847691669504

Further details:

• I have reviewed the TAG's API Design Principles

• The group where the work on this specification is being done: WICG

• Major unresolved issues with or opposition to this specification:

  Other browser vendors have expressed desires to implement various subsets of the API, so we have broken down the API into 4 separate sections that can be implemented independently.

  1. Query API
  2. Modifications API
  3. Change Events API in documents
  4. Change Events API in service workers

• This work is being funded by: Google

We'd prefer the TAG provide feedback as:

💬 leave review feedback as a comment in this issue and @-notify @ayuishii