Closed Bug 1763130 Opened 10 months ago Closed 8 months ago

Handle navigation for frames for browsingContext.navigate

Categories

(Remote Protocol :: WebDriver BiDi, task, P1)

task
Points:
2

Tracking

(firefox103 fixed)

RESOLVED FIXED
103 Branch
Tracking Status
firefox103 --- fixed

People

(Reporter: jdescottes, Assigned: Sasha)

References

(Blocks 1 open bug)

Details

(Whiteboard: [webdriver:m4], [wptsync upstream])

Attachments

(1 file)

Follow up to handle more specific navigation use cases.
We should support navigation for inner frames, both for same origin or cross origin scenarios.

Basic frame navigation should already work, this might only be about adding more tests to cover this.

Whiteboard: [webdriver:backlog]

As discussed we will try to have a look next week as long as we are working on navigation in M3. For this bug we most likely only require some wdspec tests to be added.

Points: --- → 2
Priority: -- → P3
Whiteboard: [webdriver:backlog] → [bidi-m3-mvp]
Assignee: nobody → aborovova
Status: NEW → ASSIGNED
Priority: P3 → P1
Whiteboard: [bidi-m3-mvp] → [webdriver:m4]
Attachment #9277918 - Attachment description: WIP: Bug 1763130 - Add wdspec test for browsingContext.navigate in frames. → Bug 1763130 - Add wdspec test for browsingContext.navigate in frames.
Pushed by aborovova@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/52fd327d05d0
Add wdspec test for browsingContext.navigate in frames. r=webdriver-reviewers,whimboo
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/34248 for changes under testing/web-platform/tests
Whiteboard: [webdriver:m4] → [webdriver:m4], [wptsync upstream]
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
Upstream PR was closed without merging
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.