-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Unable to find element with Internet Explorer through selenium hub #4800
Comments
The IE driver (and indeed no driver implementation) has used |
@jimevans So why this only happens with IE driver using the hub ? |
Because the IE driver now supports the W3C WebDriver Specification dialect of the wire protocol used for communication. In prior versions, the driver would return an element representation that used both keys in the dictionary. It no longer does so. I strongly suspect that if the language bindings used |
My guess was if it doesn't work, it doesn't work for both stand-alone and hub. @jimevans It's not possible to keep both keys in the dictionary ? This way, it'll give us some time to make the proper change in the bindings. The support of the W3C spec is currently in progress in the facebook php bindings. |
Also, which version should I use to avoid this problem ? |
Answering last question myself, IEDriverServer 3.4 does the trick ! |
@paulbriton You saved my day. 3.4 worked for me. Thanks a lot!!! |
Meta -
OS: Windows 10
Selenium Version: 3.6
Browser: Internet Explorer
Browser Version: IE11
Expected Behavior -
Finding an element with any available selector using Selenium hub.
Actual Behavior -
"Element not found" or "Undefined index: ELEMENT"
Steps to reproduce -
I'm using Facebook PHP bindings in this example, but I can reproduce with old PHPUnit ones too. The issue only happens when using the hub mode. Provided test case should be simple enough to be translated to another bindings.
The text was updated successfully, but these errors were encountered: