Prevent close of Bidi tab when calling closeWindow classic

[christian-bromann]

If some calls the WebDriver classic command closeWindow it will close the whole window including the Bidi tab which makes it impossible (from a framework perspective like WebdriverIO) to re-act on it and open a new window.

What are your recommendations here or would you consider this a bug in Chromedriver?

[OrKoN]

I think it is a bug in ChromeDriver (possible a regression). I do not think the window with the bidi tab should be observable.

[OrKoN]

@sadym-chromium PTAL

[sadym-chromium]

Closing last tab should close the session and the browser, and I believe it's the way ChromeDriver works in pure classic mode as well. From your perspective, what is the expected behavior after the last tab is closed? Please note that Mapper tab is transparent for the protocol.

[christian-bromann]

what is the expected behavior after the last tab is closed?

I actually learned that the session is being closed when all windows are being closed. Now this all makes sense as I tried to call browsingContextCreate which just started to hang the process since WebdriverIO never received a socket response.

Honestly I would have expected that the session remains open and I can open a new tab to continue while other commands that require a window would fail. Closing the session should only happen via the session.end IMHO. This gives me as a framework author a mean to recover from an unwanted situation where all windows got closed unintentionally.

I am sure there is a good reason to also just close the issue. Feel free to close the issue as it works as defined in the spec. Thanks for your input!

[OrKoN]

Looks like I misunderstood the original issue, the WebDriver spec indeed says that the session must end if no more top-level browsing contexts remain open according to https://w3c.github.io/webdriver/#close-window (in that sense the bidi tab is not observable as it does not prevent ending the session).