You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Minimalexample is goto any website(chat.openai.com,googleoauthpage,etc)theuseswebsocketsandusewaitForNetworkIdle.
Error string
Timeout error
Bug behavior
Flaky
PDF
Background
Websockets is not a valid "pending" connection and should be considered network idle or there should be an option to ignore websockets. Using networkidle0 or networkidle2 events of page.goto is not a solution due to the full page navigation requirement which is not compatible with app-like interfaces of modern web that use SPA or ajax.
Expectation
waitForNetworkIdle should return regardless of WebSocket connections.
Reality
waitForNetworkIdle does not return and will timeout even with concurrency set to some arbitrary number.
Puppeteer configuration file (if used)
Defaultconfig.
Puppeteer version
22.6.2
Node version
18.18.0
Package manager
npm
Package manager version
9.8.1
Operating system
Windows
The text was updated successfully, but these errors were encountered:
OrKoN
changed the title
[Bug]: WaitForNetworkIdle rarely works and fails to return during network idle conditions.
[Feature]: Add ability to exclude web sockets from WaitForNetworkIdle
May 6, 2024
Minimal, reproducible example
Error string
Timeout error
Bug behavior
Background
Websockets is not a valid "pending" connection and should be considered network idle or there should be an option to ignore websockets. Using networkidle0 or networkidle2 events of page.goto is not a solution due to the full page navigation requirement which is not compatible with app-like interfaces of modern web that use SPA or ajax.
Expectation
waitForNetworkIdle should return regardless of WebSocket connections.
Reality
waitForNetworkIdle does not return and will timeout even with concurrency set to some arbitrary number.
Puppeteer configuration file (if used)
Puppeteer version
22.6.2
Node version
18.18.0
Package manager
npm
Package manager version
9.8.1
Operating system
Windows
The text was updated successfully, but these errors were encountered: