Is it possible to run a driver/drivers in headless mode? about xenon

[stevepryde]

I've had a look into this and confirmed that the headless flag is not working.

After some investigation I discovered that the goog:chromeOptions JSON is indeed sent with the alwaysMatch capabilities, so I'll need to update Xenon to pass those through.

The reason it strips some capabilities out there is because if we do the filtering ourselves in Xenon, we don't want chromedriver also doing its own filtering and deciding not to run the session we send to it.

It's easy enough to just pick out the goog:chromeOptions and moz:firefoxOptions keys and pass those through specifically, or alternatively I can try just passing through the alwaysMatch JSON verbatim and let it fail if the client does something wrong. The latter is probably the better option.

[stevepryde]

And confirmed that works if I pass through all of the capabilities verbatim.
I've pushed the fix to latest main branch so if you pull that and try again it should hopefully work. Let me know how it goes.

I have not tested the impact this has on filtering. We can address that later if there is an issue (perhaps we can strip out the browserName, browserVersion and platformName if we need to).

[stevepryde]

Also consider running via xvfb instead (see instructions at the bottom of the README) which allows you to vnc in and view the session if you need to.

Either way you would still need the above fix in order to pass through any other chrome/firefox options

[zhiburt]

I can confirm that after 3b106ec headless works 👍