[Feature] BrowserContext.maximizeWindow()

Selenium feature: https://www.selenium.dev/selenium/docs/api/py/webdriver_remote/selenium.webdriver.remote.webdriver.html#selenium.webdriver.remote.webdriver.WebDriver.maximize_window

Requested via Slack.

Scenario: Automate a website and then let the user complete something. Its great if the max possible width/height could be determined so the user has “maximum available viewport”.

But not sure how or if its easy implementable since we in CR e.g. emulate the viewport independent from the window size.

For Chromium it works already like that:

// @ts-check
const playwright = require('playwright');

(async () => {
    const browser = await playwright.chromium.launch({
      args: ["--start-maximized"],
      headless: false,
    });
    const context = await browser.newContext({
      viewport: null
    });
    const page = await context.newPage();
    await page.goto('http://whatsmyuseragent.org/');
    await browser.close();
})();

[azad-derakhshani-GS]

@azad-derakhshani-GS This looks backwards to me: maximize would make pages behave differently, while fixed viewport guarantees consistent behavior. What do I miss?

A well-designed page behaves consistently across different viewports, so this is nothing for the testautomation framework to worry about. Trust me, in several years of TA experience, maximizing the browser window never caused any such issues, not even once. It’s also closer to the way a real user would behave. But Playwright artificially shrinks the viewport so the pages aren’t even displayed in full, which (despite it scrolling into elements) leads to page elements not being fully displayed while PW interacts with them.

Also to elaborate a bit further on the second point from my previous post: Not having a flexible (= maximized) resolution means I have to define a specific screen resolution (even null does mean 1280x720). But a static resolution could be incompatible with other people’s screens. Sizing the browser window flexibly via maximize eliminates that problem.

[starosta357]

Solution for Java: