Handle future Chrome version making document.domain immutable

[chrisbreiding]

What would you like?

Chrome is planning to make document.domain immutable.

In Chrome 100, setting document.domain will display the following warning in the Issues panel.

In Chrome 106 (due for release in April 2022), support for setting document.domain will be removed. It will log the following warning in the console and setting it will silently fail, causing a cross-origin error to be thrown when Cypress attempts to interact with the AUT. The exact release is subject to change based on the response to the Intent to Ship.

Mitigation

This issue can be mitigated by attaching a Origin-Agent-Cluster: ?0 header to the top page's request, any requests for the AUT frame's src, and any requests for the spec frame and support file frame. That will allow document.domain to be set as needed.

More Information

• Chrome blog announcement
• RFC
• document.domain docs

Why is this needed?

Cypress relies on setting document.domain so that a test can visit multiple subdomains under the same super-domain in a single test.

Once support for setting document.domain is removed, tests that rely on that behavior will no longer function and will fail with a cross-origin error.

Other

No response

[cypress-bot]

The code for this is done in cypress-io/cypress#20405, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 9.5.2.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.5.2, please open a new issue.