Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Disable "ImprovedCookieControls" feature in Chromium by default #2072

Closed
alexduhanov opened this issue May 1, 2020 · 6 comments · Fixed by #2073
Closed

[Feature] Disable "ImprovedCookieControls" feature in Chromium by default #2072

alexduhanov opened this issue May 1, 2020 · 6 comments · Fixed by #2073
Assignees

Comments

@alexduhanov
Copy link

alexduhanov commented May 1, 2020

Chromium 84.0.4131.0 includes the flag "Enable improved cookie controls UI in incognito mode" turned on by default, which will block third party cookies in Incognito mode.

Given that Playwright runs its tests in Incognito mode by default, this may be disruptive to users.

I was able to get around the issue by setting this flag to the browser launch options:

args: [
    '--disable-features=ImprovedCookieControls',
],

But it may be of benefit to others to have Playwright launch Chromium with this option disabled by default.

Note: this only seems to affect headful runs.

@pavelfeldman
Copy link
Member

@alexduhanov do you have a repro this this one? I have a test that passes on Chromium and allows third party cookies both in persistent and non-persistent contexts...

@alexduhanov
Copy link
Author

@pavelfeldman is your test running in headful mode? the issue doesn't seem to affect headless chromium

@alexduhanov
Copy link
Author

alexduhanov commented May 4, 2020

@pavelfeldman - I don't have a repro for this one as I'm hitting a proprietary login server in my actual test, but I can confirm that the flag allows my test to pass.

How were you able to test the third party cookies? Since the cookie must exist on a different domain, I'm not sure how to do this myself without a remote service that my test can talk to, or through some hosts file manipulation.

@aslushnikov
Copy link
Collaborator

How were you able to test the third party cookies?

@alexduhanov You can use http://localhost and http://127.0.0.1 as two different origins (this is what is done in https://github.com/microsoft/playwright/pull/2073/files).

@pavelfeldman
Copy link
Member

I think these are all aligned and tested now. Please feel free to reopen.

@alexduhanov
Copy link
Author

I haven't had any issues, thanks so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants