Open
Bug 1891028
Opened 7 months ago
Updated 7 months ago
Opening a tab or window should potentially wait for the "browser-delayed-startup-finished" notification
Categories
(Remote Protocol :: Agent, enhancement, P2)
Remote Protocol
Agent
Tracking
(Not tracked)
NEW
People
(Reporter: whimboo, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [webdriver:backlog])
Right now we only wait for this notification for the initial window, but not when using any WebDriver BiDi or Marionette commands to open a new context. As such our commands may return too early and causing issues. See bug 1837949 comment 5.
I would wait with any work here until bug 1837949 has been fixed to not influence test scenarios and make it harder to see.
|
||
Updated•7 months ago
|
Summary: Opening a tab or window should potentiall wait for the "browser-delayed-startup-finished" notification → Opening a tab or window should potentially wait for the "browser-delayed-startup-finished" notification
|
Reporter | |
Updated•7 months ago
|
Priority: -- → P2
Whiteboard: [webdriver:backlog]
You need to log in
before you can comment on or make changes to this bug.
Description
•