-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Chrome 128 - window-size is ignored (chrome-for-testing, headless, linux) #638
Comments
I found that : https://chromium.googlesource.com/chromium/src/+/b9b39a430f71c710d16aafcc67278ef77440c18d
It seems that headless mode is changing, and we can use Any hint on how to set size with new headless ? |
According to their docs, the It's maybe a bug in Chrome? |
Thanks for your time and feedback @dunglas :) I reported it here : https://issues.chromium.org/issues/362522328 |
This worked for me. Just in case, someone is looking for a quick solution. I am not sure if the bug is solved.
|
I had the same exact issue as OP with Chrome v130. The only solution for me was to use |
Had problem with setting window-size and setting the download directory via Using
instead of
fixed it for me. |
Yes, but this is short term as Chrome devs say "We're happy to announce that the old Headless mode will be removed in Chrome 132" (source : https://developer.chrome.com/blog/removing-headless-old-from-chrome). For now, I've switched to chrome-headless-shell (https://developer.chrome.com/blog/chrome-headless-shell). |
I have a Symfony app (7.1).
For e2e tests I use phpunit + symfony/panther + Chrome for Testing headless (on Debian Linux bullseye).
Since Chrome 128 has been released, my CI fails as the
--window-size
chrome argument is ignored.I wrote a reproducer here : https://github.com/yblatti/repro-panther-screen-size-chrome
It seems to indicates that this has been introduced with Chrome 128.0.6575.0.
I have tried to have a look at https://chromium.googlesource.com/chromium/src/+log/128.0.6542.0..128.0.6543.0?pretty=fuller&n=10000
... but this way out of my league.
The text was updated successfully, but these errors were encountered: