Bug 295084

Summary: [WebDriver][BiDi] Fix browsingContext.close error reported when the window is already closed
Product: WebKit Reporter: Lauro Moura <lmoura>
Component: WebDriverAssignee: Lauro Moura <lmoura>
Status: RESOLVED FIXED    
Severity: Normal CC: bburg, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Lauro Moura
Reported 2025-06-26 21:41:32 PDT
imported/w3c/webdriver/tests/bidi/browsing_context/context_destroyed/context_destroyed.py::test_unsubscribe The test itself works fine, but its fixture `new_tab` expects `NoSuchFrame` to be returned when the newly created tab was closed. This aligns with the "get a navigable" behavior, which is: https://w3c.github.io/webdriver-bidi/#get-a-navigable > If there is no navigable with navigable id navigable id return error with error code no such frame Our current `browsingContext.close` implementation uses `WebAutomationSession::closeBrowsingContext()`, which focus on the current top level browsing context as usual in WebDriver classic commands, returning a different error: https://w3c.github.io/webdriver/#close-window > If session's current top-level browsing context is no longer open, return error with error code no such window. Patch incoming.
Attachments
Lauro Moura
Comment 1 2025-06-26 22:09:25 PDT
Radar WebKit Bug Importer
Comment 2 2025-07-03 21:42:13 PDT
EWS
Comment 3 2025-07-09 21:06:51 PDT
Committed 297198@main (4c43756c1f6f): <https://commits.webkit.org/297198@main> Reviewed commits have been landed. Closing PR #47280 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.