246621 – chrome.tabs.create in existing window behaves incorrectly

Bug 246621 - chrome.tabs.create in existing window behaves incorrectly

Summary: chrome.tabs.create in existing window behaves incorrectly

Status:	NEW

Alias:	None

Product:	WebKit
Classification:	Unclassified
Component:	WebKit Extensions (show other bugs)
Version:	WebKit Nightly Build
Hardware:	Unspecified Unspecified

Importance:	P2 Normal
Assignee:	Nobody

URL:
Keywords:	InRadar

Depends on:
Blocks:

Reported:	2022-10-17 05:02 PDT by Carlos J.
Modified:	2022-11-10 04:25 PST (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Carlos J. 2022-10-17 05:02:33 PDT

When using chrome.windows.getAll to get a list of all windows. On iOS, you get two windows, 1 normal and 1 private. Say the current tab is a non private window. And you then try to open a window in private in the extension. It opens kinda a ghost private window which hosts inside the non-private window. Correct behaviour is that it simply opens that tab in the only private window possible. See attachments for a sample extension and reproduction video.

Sample extension and reproduction video:
https://github.com/carlosjeurissen/webext-tech-demo-extensions/tree/main/issues/safari-9653213-ios-open-in-existing-window

Comment 1 Carlos J. 2022-10-17 05:02:54 PDT

See also:
https://feedbackassistant.apple.com/feedback/9653213
https://developer.apple.com/forums/thread/690774

Comment 2 Alexey Proskuryakov 2022-10-17 10:23:42 PDT

Thank you for the report! This is most likely a Safari issue, but I'll let Tim close the report as appropriate.

rdar://83529900

Comment 3 Timothy Hatcher 2022-10-24 13:26:06 PDT

We are tracking bugs in Bugzilla for Web Extensions now as we move extensions support from Safari to WebKit.