2

I just got updated to Windows 10 (x64). My old desktop had IE 11 but a lower version, as it was running Windows 7. I now have the following IE version:

Version: 11.648.17134.0
Update Versions: 11.0.115

I downloaded the latest IEDriverServer.exe that Selenium gave me (3.14). When I run it, when I do the get(url) (various urls), afterwards it fails to find elements. I looked and noticed that before the get(), driver.getWindowHandles() had one entry, but after the get() it had zero entries. This is the latest version. I tried setting compatibility mode but that did not do any good (set or not set). The tests will work fine with Chrome but someone else wrote the test and did not verify values were non-null before calling element.sendKeys(str), which IE appears to allow but Chrome throws an exception. And there are so many instances.

So, I need to find the correct IEDriverServer for my Windows 10 IE but I am having trouble doing so. Google did not give me much except it led me to the driver I already downloaded.

Can anyone help?

undetected Selenium
  • 183,867
  • 41
  • 278
  • 352
Tony
  • 1,127
  • 1
  • 18
  • 29

1 Answers1

2

As a thumb-rule you can always use the released IEDriverServer from the respective released Selenium clients.

As an example,

  • If you are using Selenium v3.14
  • Download, extract and use IEDriverServer_Win32_3.14.0.zip or IEDriverServer_x64_3.14.0.zip
  • Snapshot:

Selenium_v3.14

Update

However to work with IE11 you have to take care of a couple of things which are beyond the scope of this discussion and are as follows:

undetected Selenium
  • 183,867
  • 41
  • 278
  • 352
  • That is the one I downloaded (the 64 version, 3.14) – Tony Mar 21 '19 at 17:47
  • Checkout my answer update and let me know the status – undetected Selenium Mar 21 '19 at 18:24
  • I did send email to a target about the key. I will check the zones again but usually it will not start up at all. – Tony Mar 21 '19 at 18:36
  • I also don't believe it is the focus problem because my driver has no windows associated with it at all after the get. – Tony Mar 21 '19 at 18:38
  • @Tony I strongly believe that though I have provided you the references but this question wasn't about _check the zones_ or _focus problem_ as such but about **IEDriverServer** _versioning_. – undetected Selenium Mar 21 '19 at 18:39
  • Yes, you were right. Previously it would warn you that the zones weren't the same, and not even start. now it does not warn you and chugs along but fails. – Tony Mar 22 '19 at 18:45