Closed Bug 1967469 Opened 10 months ago Closed 10 months ago

"browsingContext.navigate" and "browsingContext.reload" with "wait=none" should resolve when navigationCommitted is emitted

Categories

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

defect
Points:
2

Tracking

(firefox141 fixed)

RESOLVED FIXED
141 Branch
Tracking Status
firefox141 --- fixed

People

(Reporter: jdescottes, Assigned: jdescottes)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [webdriver:m16][webdriver:relnote] )

Attachments

(1 file)

After browsingContext.navigationCommitted is implemented in Bug 1945184 we should update the implementation of browsingContext.navigate to only resolve when navigationCommitted is emitted when wait=none is provided.

This also applies to browsingContext.reload given that it has a wait argument as well and makes use of the awaitNavigation() helper.

Blocks: 1750549
Summary: browsingContext.navigate with wait=none should resolve when navigationCommitted is emitted → "browsingContext.navigate" and "browsingContext.reload" with "wait=none" should resolve when navigationCommitted is emitted
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Severity: -- → S3
Points: --- → 2
Priority: -- → P2
Whiteboard: [webdriver:m16]
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4b8c7ec1d262 [bidi] Update browsingContext.navigate and reload to wait for navigationCommitted r=webdriver-reviewers,Sasha
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 141 Branch
Whiteboard: [webdriver:m16] → [webdriver:m16][webdriver:relnote]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: