Get Named Cookie seems broken for multiple cookies with the same name
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Get Named Cookie seems oblivious to the fact that there can be multiple cookies with the same name in the same context, e.g. through having a different Path. The spec (which seems broken in various ways) seems to assume that there is only one cookie with a given name.
We could refer to the sorting (step 2) in the Cookies RFC (though that mentions it might not be reliable), but it's probably preferable to simply integrate with the new Cookie Layering spec instead.
Ideally, we should offer a way to get all Cookies of the same name.
cc @annevk @dcthetall
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the WebDriver Get Named Cookie section first, then compare RFC 6265 section 5.4 and the referenced Cookie Layering specification. Done means the specification has an agreed rule for duplicate-name cookies and clearly defines whether callers can retrieve all cookies with the same name.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100