-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Parse domains/subdomains/tld using public suffix #802
Comments
do you guys have an ETA on this or a suggestion of where to start with this? |
This was referenced Jan 8, 2018
Same here. I can't get it running locally because my test domain contains "local" (and sorry, no, that's not easy to be changed in our setup). |
brian-mann
added a commit
that referenced
this issue
Feb 4, 2018
* server: fixes #802 and fixes #380 and fixes #402 and fixes #493 and fixes #1161 - use the public suffix when parsing tld’s so that document.domain is set correctly * driver: move location spec back into cypress tests * server, driver: fixes: #600 and fixes #1175 use public suffix for parsing tld, handle multiple different subdomains on cy.visit
Released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently Cypress does a naive attempt at determining the domain, subdomain, and TLD of the current application under test.
It does not consider the public suffix, which results in it setting incorrect
document.domain
as well as yelling about changing domains when it's really not.We should package in this npm module and then either make calls for parsing async (and do it in node) or transfer the data to Cypress during its bootstrap phase so it can parse it in the driver correctly.
Related to #380 and #600
The text was updated successfully, but these errors were encountered: