Closed
Bug 1894305
Opened 3 months ago
Closed 3 months ago
browsingContext.create should not wait for visibility change before waiting for navigation
Categories
(Remote Protocol :: WebDriver BiDi, task, P3)
Remote Protocol
WebDriver BiDi
Tracking
(firefox127 fixed)
RESOLVED
FIXED
127 Branch
| Tracking | Status | |
|---|---|---|
| firefox127 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
(Whiteboard: [webdriver:m11][webdriver:relnote])
Attachments
(2 files)
We are now waiting for the visibility of the previous tab to change before we wait for the initial navigation.
Overall it seems unnecessary to delay calling waitForInitialNavigationCompleted, we should probably fix this to see if it has any impact on Bug 1893921.
|
Assignee | |
Comment 1•3 months ago
|
||
|
||
Updated•3 months ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•3 months ago
|
||
Depends on D209047
This additional log could help debug what happens on the Github macos-latest workers
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b575c0618940 [bidi] Do not delay calling waitForInitialNavigationCompleted in browsingContext.create r=webdriver-reviewers,whimboo https://hg.mozilla.org/integration/autoland/rev/e1891217bb85 [bidi] Add new trace log for Navigate:waitForInitialNavigationCompleted r=webdriver-reviewers,whimboo
|
||
Comment 4•3 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/b575c0618940
https://hg.mozilla.org/mozilla-central/rev/e1891217bb85
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
status-firefox127:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
|
|
Assignee | |
Updated•3 months ago
|
Points: --- → 2
Priority: -- → P3
Whiteboard: [webdriver:m11]
|
||
Updated•2 months ago
|
Whiteboard: [webdriver:m11] → [webdriver:m11][webdriver:relnote]
You need to log in
before you can comment on or make changes to this bug.
Description
•