Closed
Bug 1838382
Opened 2 years ago
Closed 2 years ago
AbortError issues after 200ms navigation timeout "No navigation detected: about:blank" when creating WebDriver session
Categories
(Remote Protocol :: WebDriver BiDi, defect)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1838381
People
(Reporter: whimboo, Unassigned)
Details
This is a clone of bug 1832891 where a fix has been landed for the initial navigation when opening new windows and tabs. But there is still an issue with the very first initial navigation during WebDriver:NewSession
right after the browser has been started.
Because we do not wait long enough and miss the additional page load, all commands that get run immediately after the new session has been created could fail because the underlying browsing context gets replaced.
There are a couple of different intermittent failures that are caused by this broken behavior. We are going to add them all to the dependency list.
We should consider this bug for M7 inclusion.
Reporter | ||
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•