[BUG] Chrome args "--start-maximized" doesn't work on macOS Big Sur 11.3.1

Context:

• Playwright Version: 1.11.1
• Operating System: macOS Big Sur 11.3.1 (Apple M1)
• Node.js version: v16.1.0
• Browser: Chrome

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and that we can run and debug locally. For example:

const {chromium} = require('playwright-chromium');

(async () => {
  const browser = await chromium.launchPersistentContext('./userDataDir', {
    headless: false,
    args: ['--start-maximized']
  });
  const page = await browser.newPage();
  await page.goto('https://playwright.dev/docs/intro');
})();

Describe the bug

The webpage launches successfully without maximized window.

[wanghongjuan]

Many thanks for your clarification again, I double confirmed that the Chrome can be maximized with old userDataDir, but failed with new userDataDir.

[yury-s]

hi @yury-s thanks for your quickly response, I tried adding viewport: null, the flag still doesn’t work, but launching the browser from terminal with the flag works well, so I think maybe this issue should be reported to here.

I tried on macOS 10.15.7 and on 11.4, on both of them Chromium doesn’t maximize when started from terminal with that flag. @aslushnikov also tried it on Big Sur and it didn’t maximize. I also tried on Big Sur on M1 with same result.