News for hackers. Stuff that matters.
Re:Puppeteer: Headless Chrome Node API by d33 on Wednesday August 16, 2017 @12:31PM (#15028828)
Because WebDriver just doesn't do.

For an example of an impossible task, try to retrieve request headers using Selenium. Browser automation getting more and more complicated the more cases you're trying to cover and in my impression WebDriver is definitely not enough. Who knows, perhaps some new version of WebDriver that I never heard of it will catch up once the functionality gets properly defined.

Re:Puppeteer: Headless Chrome Node API by bauerd on Wednesday August 16, 2017 @12:42PM (#15028934)
Yes, I wholeheartedly agree, it was a stupid decision by the Selenium devs not to make request headers etc. accessible. But why throw all the standardisation efforts overboard?
Re:Puppeteer: Headless Chrome Node API by fake-name on Wednesday August 16, 2017 @04:20PM (#15031013)
I think this is more "selenium is actively antagonistic to it's major use-case", then trying to throw everything away. There have been multiple attempts to convince the selenium people to revisit their decision W.R.T. headers, and they're completely unwilling.

Given that the selenium leadership is apparently uninterested in improvements, and it's many limitations, trying to improve there is more effort then it's worth.

Re:Puppeteer: Headless Chrome Node API by kensoh on Thursday August 17, 2017 @02:26AM (#15034223)
I didn't follow that development. Can you share why Selenium maintainers chose not to implement headers? Is it that they want to restrict the tool to simulate what a normal user can do with a browser and not hacks such as overriding headers? Thanks in advance!
Re:Puppeteer: Headless Chrome Node API by fake-name on Thursday August 17, 2017 @01:22PM (#15038796)
"Something something something normal users can't do that something something".

Basically, they're still stuck in this idea that they're ONLY for emulating user-available input (and the dev-tools don't exist).

In reality, there is tremendous interest in more complex programmatic interfaces, but apparently they're unwilling to see that, and are instead only interested in their implementations "user-only" ideological purity.

Re:Puppeteer: Headless Chrome Node API by onion2k on Thursday August 17, 2017 @03:14AM (#15034441)
For an example of an impossible task, try to retrieve request headers using Selenium.

Selenium can't do that itself but Selenium can drive a browser that uses a proxy and you can retrieve everything about the request from that. It's a lot more challenging if you're testing things that use SSL but it's not impossible with a decent proxy app (eg Charles).