4 ms·
The problem with ChromeDriver is that it implements Selenium's idea of what the remote control interface should look like, and frankly speaking, Selenium's idea
by fake-name 9y ago
The problem with ChromeDriver is that it implements Selenium's idea of what the remote control interface should look like, and frankly speaking, Selenium's idea has some enormous and idiotic oversights[1].
[1] http://stackoverflow.com/questions/3492541/how-do-i-get-the-response-headers-in-selenium http://stackoverflow.com/questions/3492541/how-do-i-get-the-...
- tlrobinson 9y agoChromeDriver also has a particularly annoying race condition when triggering clicks https://bugs.chromium.org/p/chromedriver/issues/detail?id=28 https://bugs.chromium.org/p/chromedriver/issues/detail?id=28 which often only appears on slow machines such as multitenant CI services like CircleCI (https://circleci.com/docs/1.0/chromedriver-moving-elements/ https://circleci.com/docs/1.0/chromedriver-moving-elements/)