[Question] New browser windows are opened instead of tabs on every newPage()

Trying to use a single browser instance with mutiple sessions (pages/ tabs), but on every newPage() a new window is launched instead of a tab.

main.js

const chromium = require('playwright').chromium;
const options =  {
  headless: false,
  timeout: 30000,
},
const browser = await chromium.launch(options);
app.set('browser', browser);

At this point browser window is not opened. (Unlike puppeteer which opens a new browser window on launch)

/lib/other.js

const browser = app.get('browser');
const page = await browser.newPage();

Now a new browser window is opened every time newPage is called, instead of opening a new page in the existing window.

So, Is this the expected behaviour with PlayWright?

NOTE: Puppeteer would open a window once (on launch) and add tabs on every newPage().

[yury-s]

So, Is this the expected behaviour with PlayWright?

Yes, this intentional behavior. Each page is opened in its own window. We had to split it for video recording to properly work in other browsers and wanted to keep it consistent across browsers. Moreover, in your code snippet each page created by const page = await browser.newPage(); will have its own context and we do not want to mix pages from separate contexts in the same window (similar to how pages from different chrome profiles could never be combined as tabs in the same window). Your code is equivalent to:

const context = await browser.newContext();
const page = await context.newPage();

Is there a test scenario that doesn’t work with separate window per page approach?

[apmcodes]

Is there a test scenario that doesn’t work with separate window per page approach?

Well, our use case is not exactly related to testing but scrapping at high volume. Thus, opening many windows paralelly would hamper the memory footprint of our apps.