The next release of Selenium features a rewritten chrome driver that
does away with the need for the "disable-web-security" flag. It should
have been out last Friday, so I expect it to be released very, very,
very soon.
Simon
> --
> You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
> To post to this group, send email to selenium-...@googlegroups.com.
> To unsubscribe from this group, send email to selenium-develo...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.
>
>
The next release of the chromedriver binary will let you pass custom
switches through DesiredCapabilities:
http://src.chromium.org/viewvc/chrome?view=rev&revision=85289
I don't think Chrome supports a --display argument though.
--
As mentioned, this will be supported in the next released build of the
Chrome server. I've also added TODO in the Ruby bindings about
exposing it to the user:
http://code.google.com/p/selenium/source/browse/trunk/rb/lib/selenium/webdriver/chrome/bridge.rb#18
Assuming you've downloaded the latest chromedriver binary, I believe
you can make it work by doing e.g.:
DesiredCapabilities caps = DesiredCapabilities.chrome();
caps.setCapability("chrome.switches",
Arrays.asList("--disable-translate", "--foo-bar=1"));
WebDriver driver = new ChromeDriver(caps);
Jari