-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W3C WebDriver protocol support #450
Comments
@shs96c sure, we are following the news about W3C Selenium standard adoption. Right now we already support working directly with latest Geckodriver releases as well as |
The spec should become a recommendation on the 31st May. Once the session is established, something like selenoid shouldn't need many changes. Things that differ are:
Feel free to hop on the #selenium IRC channel on Freenode or our Slack channel (which is mirrored to IRC) if you'd like clarification on any of the areas or to talk about implementation strategies. |
@shs96c ok, thanks. |
Also need to correctly process |
Ok, we decided to just ignore |
The java bindings will fill firstMatch if necessary, and some of the other language bindings prefer using firstMatch to alwaysMatch. I’d consider reopening this. The algorithm for converting the New Session payload is incredibly simple: just merge alwaysMatch into every firstMatch and throw an error if there are duplicate keys. Then just iterate over the generated list and find the first one your hub supports. |
@shs96c ok, let's reopen and see what could be done with it. |
Supporting firstMatch in capabilities (fixes #450)
The next major release of Selenium (version 4) will see a major change in the wire protocol: language bindings will move from supporting the original wire protocol to the new W3C webdriver protocol. Specifically, we expect the .Net, Ruby, Python, and JS bindings to all only support the webdriver protocol. It is likely that additional effort will need to be taken by Java developers to continue using the original wire protocol.
Selenoid needs to support the matching algorithm outlined in the spec, as well as ensuring that metadata is passed through to downstream nodes.
Our current working estimate is that Selenium 4 will ship before October, 2018, though (as with all OSS) this is only our own estimate.
The text was updated successfully, but these errors were encountered: