[Question] Ability to disconnect from browser server without closing contexts

Hi, is it possible to disconnect from a browser server while keeping open the browser contexts that were opened?

In puppeteer, the browser.disconnect method does this. It looks like playwright doesn’t have a disconnect method, just a close that disconnects and closes the browser contexts

[PeterCassell92]

I am also in need of this feature.

My use case: I am running automated tests for applications in an embedded browser (powered by Chromium) and I am connecting Playwright using Chromium.connectOverCDP(). The embedded browser (deliberately) has limited functionality so newPage() is not valid here and neither is browserContext.close(). There can only ever be one browser context and one page per instance of the desktop application. In the jest environment setup, I connect to using connectOverCDP() however in the environment teardown I cannot use browserContext.close() as closing the browser context will close the desktop application (and therefore will disrupt other tests).

In puppeteer, I used to use browser.disconnect() and this worked because it does not try to close the browserContext, allowing my jest tests to finish correctly, with no open processes. I would like to know how to achieve the same result in Playwright or suggest a similar feature for a future release.

[calebeby]

Thanks for clarifying. Unfortunately Jest force-kills test processes that don’t terminate gracefully, so that’s not an option for me:

I’ll be sticking to Puppeteer for now, thanks for your help anyways!