Bug 327999

Summary: [WebDriver][BiDi] browsingContext.create should honour the background parameter and place a new tab next to its reference
Product: WebKit Reporter: Timothy Olusanya <seunxplicit>
Component: WebDriverAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: bburg
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=286790
https://bugs.webkit.org/show_bug.cgi?id=288324

Timothy Olusanya
Reported 2026-10-18 07:50:02 PDT
> browsingContext.create ignores the background parameter and does not activate the context it creates. With > background false (the default) the new context must be visible and focused when the command returns; with > background true it must be created without taking focus, leaving the current context visible. On the GLib > ports the new page is never activated because the automation client does not implement > requestSwitchToPage (bug 288324), which also keeps browsingContext.activate a no-op. A tab created with a > referenceContext should also open in the reference's window, after it, rather than wherever the embedder puts it. > Covered by WPT browsing_context/create/background.py (all six rows) and browsing_context/create/type.py > (test_type[tab] and test_type[window], which check that the original tab is hidden and unfocused after a tab is > created and that the original window stays visible but unfocused after a window is created). On GTK the two > window rows of background.py pass only by accident of Xvfb focus. Last part of bug 286790. > Spec: https://w3c.github.io/webdriver-bidi/#command-browsingContext-create
Attachments
Alexey Proskuryakov
Comment 1 2026-10-18 16:37:46 PDT
*** This bug has been marked as a duplicate of bug 328000 ***
Note You need to log in before you can comment on or make changes to this bug.