Step 6 of Add Cookie spec unclear
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
In chapter 14. Cookies, section 14.3 Add Cookie:
cookie domain is not equal to the current browsing context’s active document’s domain
It is unclear whether this "not equal" should be interpreted literally, or if this is meant to be a set-like equivalence.
For example, if the user was currently on the site "foo.bar.com", the current spec (if taken literally) would not allow the user to set a cookie for "bar.com", which he/she should be allowed to do. A clarification or rewording would be much appreciated.
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 linked WebDriver sections 14.3 Add Cookie and 14. Cookies, then examine the stated domain rule and the foo.bar.com versus bar.com example. Clarify whether “not equal” is literal or reflects set-like domain equivalence, and update the specification wording so the intended cookie behavior is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100