Selenium HeadLess Bug in Chrome/Edge 129.x version - Blank Window Appearing

Selenium HeadLess Bug in Chrome/Edge 129.x version - Blank Window Appearing

Schedule a meeting in case of any queries/guidance/counselling:

~~~Subscribe to this channel, and press bell icon to get some interesting videos on Selenium and Automation:

Follow me on my Facebook Page:

Let's join our Automation community for some amazing knowledge sharing and group discussion on Telegram:

Naveen AutomationLabs Paid Courses:
GIT Hub Course:

Java & Selenium:

Java & API +POSTMAN + RestAssured + HttpClient:

[mattyb]

Good call with the window position. I was using the "=old" option, but that introduced other issues for me, in addition to being only a temporary solution, as you mentioned. For others' reference, I'm using Kotlin/Selenide, and for those wondering about the other issues: I had a few tests start failing when they were unable to find toast messages as soon as I switched to "headless=old". I set up screenshots, which revealed that the toast messages in question weren't appearing at all, but it all works fine with headless=new.

[subhuvijay]

Faced the same issue yesterday. Thanks for the workaround solution

[muhammadfarisadnan]

Thanks alot, this really helpful video.

[arjavvirani]

Yes, it's the bug
And by passing arguments as shown, that window now disappeared. Thanks.

[choirofhope]

Thank you sir! adding argument '--headless=old' worked for me for chromedriver 129.0.6668.89.

[bjosmilesu]

I’m executing my test cases using gitlab runner and my screenshots are captured as blank . I wonder if this could be the reason why I’m getting the error

[sagars]

No I did not face this issue today on running in headless mode

[jackychandran]

we tried this workaround in latest chrome, still getting white blank screen

[GurudattaPraharaj]

Playwright Headless mode is working much better than selenium headless