GoogleChromeLabs / GoogleChromeLabs/chrome-for-testing
Third Party Cookies
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 159
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 3
Description
It seems to me that third party cookies are disabled by default in Chrome for Testing.
In my opinion it does not make sense, as Google [recently announced](https://privacysandbox.com/news/privacy-sandbox-update/) they are not going to deprecate third party cookies.
I use Chrome for Testing for testing of my project, that sometimes utilizes third party cookies and cannot properly use Chrome for Testing because of that.
Contributor guide
Research direction
Reproduce the reported behavior in Chrome for Testing with a project that uses third-party cookies, then identify the configuration or packaging entry point responsible. Done means third-party cookies behave as expected for the intended policy without breaking existing browser tests; the issue names no files or tests, so repository exploration is required.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100