-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Handle cross-origin document.cookie #22479
Labels
topic: cookies 🍪
topic: cross-origin ⤭
Topics related to cross-origin navigation in tests
topic: cy.origin
Problems or enhancements related to cy.origin command
Comments
chrisbreiding
added
topic: cookies 🍪
topic: cross-origin ⤭
Topics related to cross-origin navigation in tests
topic: cy.origin
Problems or enhancements related to cy.origin command
experiment: origin
labels
Jun 23, 2022
4 tasks
2 tasks
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: internal
labels
Jun 29, 2022
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Jun 30, 2022
The code for this is done in cypress-io/cypress#22594, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
topic: cookies 🍪
topic: cross-origin ⤭
Topics related to cross-origin navigation in tests
topic: cy.origin
Problems or enhancements related to cy.origin command
The cross-origin cookie handling currently handles setting/getting cookies via http requests, but cookie setting/getting in-browser via
document.cookie
does not work if the AUT is on a different origin than top.Need to monkey-patch
document.cookie
and override its setter and getter, so that it simulates what it would do if the AUT was run in the top frame.The text was updated successfully, but these errors were encountered: