Headless Browser in Chrome 137 suddenly stopped maximising or windows size is not set 1920*1080. Below is my robot keyword. Does any one face this issue when running headless with latest chromedriver. Any help much appreciated please?

Libraries SeleniumLibrary
1

Use Chrome Browser for UIAutomation
${prefs}= Create Dictionary
… profile.default_content_setting_values.automatic_downloads=1
… download.default_directory=${default_download_directory}
… download.prompt_for_download=False
${chrome options}= Evaluate sys.modules[‘selenium.webdriver’].ChromeOptions() sys, selenium.webdriver

Call Method    ${chrome options}    add_argument    ${browsermode}
Call Method    ${chrome options}    add_argument    --start-maximized
Call Method    ${chrome options}    add_argument    --disable-gpu
Call Method    ${chrome options}    add_argument    --disable-extensions
Call Method    ${chrome options}    add_argument    --disable-sync
Call Method    ${chrome options}    add_argument    --no-default-browser-check
Call Method    ${chrome options}    add_argument    --no-first-run
Call Method    ${chrome options}    add_argument    --no-sandbox
Call Method    ${chrome options}    add_argument    --disable-dev-shm-usage
${log_level}=    Evaluate    "--log-level=3"
${window_size}=    Evaluate    "--window-size=1920,1080"
Call Method    ${chrome options}    add_argument    ${log_level}
Call Method    ${chrome options}    add_argument    ${window_size}
Call Method    ${chrome options}    add_experimental_option    prefs    ${prefs}

Create Webdriver    Chrome    options=${chrome options}
2

Hi, I’ve had this problem for a couple of weeks now.
Chrome update broke headless, all chrome driver options failed for me, tried many, including ones in your code.
If no one has a solution, I’m afraid we’ll have to wait for bugfix by Google. :frowning:
For reference, here’s a link I found today: [🐛 Bug]: ChromeDriver not honoring the --window-size parameter · Issue #15827 · SeleniumHQ/selenium · GitHub

1 Like
3

did anyone find any solution to this ?

4

Yes, just today.
In your headless ChromeOptions browser - do NOT use ‘Maximize Browser Window’.
Instaed, in its config, just use flag:
--window-size=1920,1080
or use keyword:
Set Window Size 1920 1080

Issue is with Selenium/Chrome - maximizing a headless window does not actually resize it to the screen size, but to a default small size (e.g. 800x600px)

5

Great that you were able to resolve your issue!
wouldn’t this mean we have to provide specific resolution values depending on the machine on which our tests run ? maximize browser window automatically adjusted that. I am running the tests remotely so that is an added issue for me

6

"wouldn’t this mean we have to provide specific resolution values depending on the machine on which our tests run ? " - No.
Just set specific size for headless. Most common screen res nowadays is 1080p or 4k, your choice. But headless apparently doesn’t care about your current display’s res.
I have a 1920x1080 px display, had Edge (mis)configured to run headless maximized, and it ran tests in 4K slight_smile:
You can use Maximize for non-headless. But yes, it’s useful to have diff configs for different browsers and modes.

7

@rofan for me this might depends of the machine, if running for example in a docker with xvfb, and window size has an importance on interaction, or if you use XY positions, screenshots comparison or else

Anyway, I had this issue on Docker/Linux since Chrome 133 when I opened this ticket Chromium that never moved…

Thing I don’t understand is we often see lately people raising this problem (Chrome 135, 136, 137), as if the problem was not there before (maybe driver was not updated)

Regards
Charlie

8

@CharlieScene
Useful link!
And yes, this is not the first time I am facing this issue. Google broke stuff and didn’t clean up after that.
As I said - workaround works - just don’t use Maximize for headless. My current Chrome version - 137.0.7151.120
As for driver - has been updated - latest stable chromedriver is 137.0.7151.119 (see link).
So maybe try updating versions in your docker image.

9

Yes on my side no problem for a while.
I’m setting the window size and position in chrome_options.
All works in both my Windows OS and Docker/Linux.

To ease test case building/debugging and interaction, I use maximize kwd only on Windows OS as I detect it when test starts