Skip to content
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 Support #553

Closed
dotnetprofessional opened this issue Sep 11, 2018 · 4 comments
Closed

W3C Support #553

dotnetprofessional opened this issue Sep 11, 2018 · 4 comments

Comments

@dotnetprofessional
Copy link

I'm in the process of trying to get IE 11 to work with WD. However, its failing, and I've tracked it down to what appears to be a lack of support for the new W3C protocol. I noticed in the code there is some mention of this support however, I didn't see any reference this this:

The web element identifier is the string constant "element-6066-11e4-a52e-4f735466cecf".

The data being returned by the IE driver has this new constant, but the WD client only understands the older .ELEMENT. Modifying the code manually did get to use this new Id did get me past my initial issues, but then other parts were broken too. So I suspect this is a larger change than one spot in the callback.js file.

It seems webdriver.io has this support, as they check for both.

@jlipps
Copy link
Collaborator

jlipps commented Sep 11, 2018

Webdriver.io is much better supported and I recommend switching to it.

Alternatively, use Selenium in front of the IE driver, as it will translate protocols for you.

@jlipps jlipps closed this as completed Sep 11, 2018
@dotnetprofessional
Copy link
Author

Thanks but the we've already built all our infrastructure around this library for mobile and we'd like to make use of it for our Web based tests as well (ie basically the same tests for all platforms). I didn't notice you had another issue tracking this #547. Is this likely to be resolved anytime soon?

@jlipps
Copy link
Collaborator

jlipps commented Sep 11, 2018

There's no one actively maintaining this project at the moment, so I'm not sure how soon it will be resolved. The quick fix is to run your tests through Selenium instead of the IE driver directly.

@admc
Copy link
Owner

admc commented Sep 14, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants