[Feature]: Add ability to exclude web sockets from WaitForNetworkIdle

[JortsEnjoyer0]

Minimal, reproducible example

Minimal example is go to any website (chat.openai.com, google oauth page, etc) the uses websockets and use waitForNetworkIdle.

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)

Default config.

Puppeteer version

22.6.2

Node version

18.18.0

Package manager

npm

Package manager version

9.8.1

Operating system

Windows

[github-actions]

This issue has an outdated Puppeteer version: 22.6.2. Please verify your issue on the latest 22.7.1 version. Then update the form accordingly.

---

Analyzer run