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.
Long story short, there seems to be a new way of running headless chrome? I’ve found this stackoverflow on the topic: selenium webdriver - Chrome 129 Headless shows blank window - Stack Overflow
The solution it proposes, to use --headless=new worked for me – the window disappears once the test is complete.
@mwinteringham I think it would be good to reflect that in FCTA (CS?) 2.4.2 – it gave me quite a headache