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
{{ message }}
Repository navigation
Time out BiDi capture calls so Chrome 156/157 popup tabs cannot hang a test #574
Chrome 156 and 157 never answer a WebDriver BiDi command that targets a tab opened by window.open() (a tab with an opener): script.evaluate, locateNodes, screenshots and input actions hang. Chromium fixed it in 158.0.8106.0 (crbug 571161446). WebdriverIO pinned its own e2e jobs to Chrome 155 because of it (webdriverio/webdriverio#16206).
Chrome 157 is the current stable release, so any user whose test opens a popup can hit this. A DevTools capture call that targets the popup and has no timeout would hang the user's test, even when the test itself never touches the popup with a BiDi command.
Several capture paths already use core/src/with-timeout.ts (action-snapshot.ts, the service and Selenium screencasts, session-metadata.ts, command-stack.ts). Not every BiDi call is covered: preload registration, the collector drain and injection, network and console subscriptions, and the Python adapter's BiDi calls need checking.
Proposal
Audit every BiDi call each adapter makes against a browsing context, in all four adapters, and list which ones have no timeout.
Put each uncovered call behind withTimeout (Python: the equivalent), so a hung command degrades capture for that tab instead of hanging the test.
Log one warning per session when a capture call times out on Chrome 156 or 157, naming the Chrome bug and the fixed version.
Document in the README and the webdriver.io docs that popup flows need Chrome 155 or 158+.
How we will know it worked
A test or example that opens a tab with window.open() and runs on Chrome 157 finishes, with the capture timeout logged, in every adapter. Record the run before (hangs) and after in the PR.
Activity