web-platform-tests / web-platform-tests/wpt
SameSite cookie tests seem to rely on third-party cookies being allowed
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6.2k
- Forks
- 3.9k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 586
Description
see, e.g., these results on wpt.fyi
"Cross-site fetches are cross-site" fails in Safari with: assert_equals: SameSite=None cookies are always sent. expected (string) "0.17879251053118983" but got (undefined) undefined
This is the expected behaviour in Safari, and is compliant with draft-ietf-httpbis-rfc6265bis-11:
While this document does not endorse or require a specific approach, it is RECOMMENDED that user agents adopt a policy for third-party cookies that is as restrictive as compatibility constraints permit. Consequently, resources cannot rely upon third-party cookies being treated consistently by user agents for the foreseeable future.
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
Start with the WPT results linked in the issue and locate the failing “Cross-site fetches are cross-site” SameSite test under cookies/samesite/fetch.https.html. Check how the test assumes third-party cookies are available and compare that behavior with the cited RFC guidance. Done means the relevant tests no longer require third-party cookies to be enabled while still testing SameSite behavior consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100