So Iāve started getting a frustratingā¦ bug? whenever starting ChromeDriver with --headless (and the exact moment when I was to use it in the FCTA courseā¦) in Windows 11 a blank window appears that canāt be interacted with, thatās not really linked to any Windows running āappā and therefore has no representation on the taskbar. It doesnāt disappear after the test is done and I could only get rid of it by blindly killing all of the 40 chrome processes in the task manager.
Headache continuesā¦ Something is still definitely wrong. After a minor Chrome update headless=new started causing the problem instead of fixing it. Worst thing is locally I get different results than in my GitHub workflow that Iāve set up for my FCTA courseā¦
Iāve taken a look at this and unfortunately because I am on Mac I am unable to reproduce this issue. However, reviewing the SO page you sent I can see there is a suggestion of adding the following:
options.AddArguments("--headless=old")
As opposed to:
options.AddArguments("--headless=new")
Have you tried it with it set to old? Iām afraid if this is a bug in Chromium I donāt know what to suggest that hasnāt already been suggested in the SO article.
I found this, but it feels like itās the same as what is shared on SO: