Closed Bug 1756532 Opened 1 year ago Closed 10 months ago

waitForInitialNavigationCompleted doesn't wait for a potential page load after about:blank

Categories

(Remote Protocol :: WebDriver BiDi, defect, P2)

defect
Points:
2

Tracking

(firefox101 fixed)

RESOLVED FIXED
101 Branch
Tracking Status
firefox101 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

(Whiteboard: [bidi-m3-mvp])

Attachments

(1 file)

Right now we are awaiting for a single page navigation to complete. And this could be the initial (synchronous) load of about:blank. But it doesn't cover a potential additional load which could also be the about:blank page or any other one.

This would also help for bug 1751643 and bug 1739540 given that both are easier to reproduce right now until bug 1754132 (too early return from WebDriver:Navigate with PageLoadStrategy of none) has been fixed.

Blocks: 1755755
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Points: --- → 2
Priority: -- → P2

This is actually a defect and not an enhancement.

Severity: -- → S3
Type: enhancement → defect
Summary: waitForInitialNavigationCompleted has to wait for a potential page load after about:blank → waitForInitialNavigationCompleted doesn't wait for a potential page load after about:blank
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/47c716300e4c
[marionette] waitForInitialNavigationCompleted has to wait for a potential page load after about:blank. r=webdriver-reviewers,jdescottes
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
No longer blocks: 1751643
You need to log in before you can comment on or make changes to this bug.