-
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
page loads successfully, but cypress throws, pageload timeout error in case cross origin and iframe type of page only in chrome. #28235
Comments
@swapnilAlgamwar Is this a new error in 13.3.2? Can you try downgrading to another version to see if this is resolved? Is the page load timeout from the first load of the page or on the cross origin page load? A reproducible example that we can run would be ideal. |
Problem met :
I had not noticed it before. How I trigger it :
Sorry I haven't had the time to make an isolated test for that. |
we have the same error being thrown when we upgrade Edge or Chrome to version 120, and its only in headless mode... the same tests pass fine in headed mode setting chromeWebSecurity 'fixes' the issue but its obviously a sub optimal workaround exact same tests run without error in headless mode in Edge or Chrome 119 or lower so assuming its related to the security changes in chromium 120 |
|
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
Current behavior
Cypress fails to detect page load event in case cross origin and iframe type of web page.
Note : same code has been working fine on electron but fails on chrome.
Desired behavior
Page load timeout should not be seen, after page load is success.
Test code to reproduce
Cypress Version
13.3.2
Node version
v18.16.1.
Operating System
Windows 10 Enterprise
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: