Closed Bug 1841470 Opened 10 months ago Closed 10 months ago

[wdspec] new_tab fixture should not raise NoSuchFrameError when trying to close the tab

Categories

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

defect
Points:
1

Tracking

(firefox117 fixed)

RESOLVED FIXED
117 Branch
Tracking Status
firefox117 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

Details

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

Attachments

(1 file)

New new_tab fixture expects that the previously opened tab is still present and as such the browsingContext.close command should not fail.

But the test could already have closed the tab. As such we should catch the NoSuchFrameError exception and at least print some information to the log.

Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cee4ab20ddee
[wdspec] "new_tab" fixture should not raise "NoSuchFrameError" when trying to close the tab. r=webdriver-reviewers,Sasha
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/40886 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
Upstream PR was closed without merging
Points: --- → 1
Priority: -- → P1
Whiteboard: [webdriver:m8]
Whiteboard: [webdriver:m8] → [webdriver:m8], [wptsync upstream]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: