Allow Delete All Cookies to delete *all* browser cookies, regardless of the current domain
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- api, documentation
Research direction
Start by reviewing the WebDriver cookie-deletion specification and compare the Chrome and Firefox behaviors described in the issue. Read the related Capybara issue for the race condition, then determine whether the spec should require browser-wide deletion or define a separate endpoint; done means the chosen behavior is explicitly specified.
Written by the indexing model from the issue text.
Description
After #1149 was applied it's not clear whether "Delete All Cookies" should delete all cookies for the current domain/origin, or if it should delete all cookies for all domains stored by the browser.
Chrome and Firefox seem to treat this differently: Chrome will delete all cookies, regardless of the current address, but Firefox will delete only those cookies associated with the current domain.
The Firefox behavior causes a race condition when resetting a browser session in tests. In our case, using Capybara (please see the related issue), we delete cookies and then navigate to about:blank. Sometimes, after cookies have been cleared, a long-running ajax request sets a new cookie just before the browser leaves the page for about:blank. Once we return to the same domain we cannot be sure that the browser didn't set any cookies (and that leads to flaky test failures).
It would help to clarify in spec that the browser should delete all cookies, regardless of the current address (i.e. to standardize Chrome behavior). Alternatively, a new API endpoint could be added that explicitly deletes all browser cookies.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
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.
More from w3c/webdriver
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
What counts as "the DOM events generated by the last invocation of the dispatch tick actions steps"? Openneeds-discussion Perform Actions
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement needs-discussion Perform Actions
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
bug Element Click Perform Actions
Difficulty 4/5 3-5 days Newbie friendliness 57/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·