How many of these can be faked with some additional code with Chrome headless?
Regardless as others are saying, using complete Chrome or Firefox with webdriver solves all these, right? Is there a way to detect the webdriver extension? That's the only difference I think from a normal browser.
> How many of these can be faked with some additional code with Chrome headless?
All of them. As soon as you can run some JS code before the page does, every single difference can be monkey-patched. There's no way to distinguish native APIs from fake APIs made by someone that knows all ways of detecting them.
or you know, run chrome in a real desktop environment. sure it might take more resources, but that's definitely cheaper than tracking down the places in chromium where you need to make the changes.
Is it? I was talking about it being more in a collective fashion and pushed into the code or done in a way where it would be easier to integrate it into Chrome headless.
I personally already do a lot of Chrome and Firefox in real desktop environment. I love doing it this way. I know I can mimic a real user. It gives me great comfort.
Still, it's only cheaper if you're doing all the tracking down yourself. And I never meant for that to be my point.
Regardless as others are saying, using complete Chrome or Firefox with webdriver solves all these, right? Is there a way to detect the webdriver extension? That's the only difference I think from a normal browser.