Some chromedriver clients, such as those that use webdriver.js, communicate
with chromedriver through cross-domain XHRs. This breaks the same-origin policy
so webdriver.js uses CORS to talk to webdriver servers.
Selenium server supports CORS through the /xdrpc (cross-domain rpc) endpoint.
Since chromedriver doesn't support this, webdriver.js users need to use
selenium server as a proxy to chromedriver, which requires pulling in java and
selenium-server as dependencies.
We can remove this requirement by implementing /xdrpc directly in chromedriver.
For reference, the selenium-server implementation was added in:
https://github.com/SeleniumHQ/selenium/commit/b49cecf13616a884393682b26299b7f146
322ff6
Original issue reported on code.google.com by samu...@chromium.org on 10 Jul 2015 at 9:39
Original issue reported on code.google.com by
samu...@chromium.org
on 10 Jul 2015 at 9:39