w3c / w3c/webdriver

Expose partitioning in serialized cookies

Open
#1,894 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Get All Cookies Get Named Cookie
Dominant language
HTML
Stars
718
Forks
228
PR merge metrics
No merged PRs in 30d

Description

WebDriver has a representation of cookies that contains some of their most relevant concepts for test introspection. It's currently missing support for the "Partition Key" of a cookie when using CHIPS. Because the partition key is more than just a site, it's a site and an ancestor chain bit (or potentially no partition key at all), it's not clear what it should serialize to.

As a straw man suggestion just to get some input, I could imagine splitting it up into two attributes:

  • cookie["partitionKeySite"], which is either a DOMString representing a site, or undefined.
  • cookie["partitionKeyHasCrossSiteAncestors"], which is a boolean that represents whether or not the partition key has the ancestor chain bit (yes this is a really long name)

Any thoughts / suggestions @annevk @dcthetall @bvandersloot-mozilla?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the WebDriver cookie representation linked in the issue and review the CHIPS partition key concept. The issue is seeking agreement on how to serialize the site and ancestor-chain information, so completion requires an accepted representation before implementation can be defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.