How to run it? about fantoccini HOT 11 CLOSED

I noticed that in the geckodriver snippet a protocol was not given.

I could be wrong but I believe the http protocol is necessary.

from fantoccini.

The following works for me:

$ chromedriver --port=4444

Client::new("http://localhost:4444");

So does just starting geckodriver and using the same Rust code to connect.
You're running these two commands on the same machine, right?

from fantoccini.

yes

from fantoccini.

now it sees the chrome driver. but

thread 'main' panicked at 'called Result::unwrap()on anErr value: NotW3C(Object({"message": String("session not created exception: Missing or invalid capabilities\n (Driver info: chromedriver=2.29,platform=Linux 4.11.5-1-ARCH x86_64)")}))', src/libcore/result.rs:859

from fantoccini.

Are you using the latest commit on master? And a recent version of Chrome + chromedriver?

from fantoccini.

yes

from fantoccini.

Seems this is happening on the latest version of Chrome for me too -- not clear why. I suspect Chrome's WebDriver implementation is deviating from the W3C spec again, so you should stick with geckodriver for now (since it's a conforming solution).

from fantoccini.

the latest version of geckodriver

thread 'main' panicked at 'unexpected webdriver error; webdriver returned error: connection refused', /home/user123/.cargo/registry/src/github.com-1ecc6299db9ec823/fantoccini-0.6.4/src/lib.rs:173
note: Run with `RUST_BACKTRACE=1` for a backtrace.

from fantoccini.

geckodriver takes a little while to start up -- make sure you wait for the server to be ready before trying to launch the Rust program. Beyond that, I don't know what to tell you. It works on my machine with geckodriver :/

from fantoccini.

Apparently the chromedriver issue is known, and has been fixed with chromedriver 2.30.

from fantoccini.

@kokinarido one workaround that might work for you for chromedriver is to replace

.map(|s| s.contains("cannot find dict 'desiredCapabilities'"))

with

.map(|s| s.contains("Missing or invalid capabilities"))

in the code. There should only be one place that it appears. This change and much more will eventually land in the next release (currently on the futures branch).

from fantoccini.