Selenium click sometimes not working using Edge driver

Not reproducible Issue #10290683


David A.
Dec 21, 2016
This issue is public.
Found in
  • Microsoft Edge
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

I’ll like to report this issue:

I don’t write it but I’ve the same problem.
I’ve created a tool to abstract the selenium API. It’s at and

I’m in process to migrate to Selenium 3 and the new edge driver. For my tool I’ve a large test suite which cover all the usage of the Selenium API. This issue is here to mainly for the checkbox case.

I’ve you want to reproduce you can use my test suite.



Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

  • Thank you for your feedback. I have been testing checkbox with Edgedriver and appears to be working as expected. Could you please share your code as a reference to see if we can reproduce with your code. This will help us investigate the issue.

    All the best,
    The MS Edge Team 

  • The sample test in in Java is it ok for you ?

  • Sure, no problem. Any languages are OK. 

    The MS Edge Team

  • Hi Ibrahim,

    The code to reproduce is here


  • Hi,

    Have you tried ?
    Have you reproduced ?
    Do you need more informations ?


  • Microsoft Edge Team

    Changed Assigned To from “Ibrahim O.” to “Steven K.”

  • Hi David,

    I am looking at this issue now.  Apologize for the delay.

    Have you have re-run these example repro’s in the latest Windows 10 releases?

  • No I’ve no tried. I’ll try wednesday

  • Hi David,

    I did not run your test suite yet as I wanted to test only the click event and repro the StackOverflow question without extra tests and tool setup, i.e. minimize the number of variables and chances for differences.  I will look at your test suite as I like the tech stack you are using.

    I created a basic repro and wanted to see if you agree that this simplified HTML will work for this.  The main difference is the surrounding label tags and simplified id’s, etc.

    The original issue on StackOverflow is not clear.  Is it the WebDriverWait() method or the proper method to click the returned element that is having the issue of not working when running without the debugger?  In the repro I created only the click event will be tested and on the WebDriverWait method.

    I have attached a sample WebDriver console application and sample HTML that needs to be hosted locally.

  • Hi Steven,

    I have also seen a similar issue. Not absolutely sure it is the same problem but if it helps this is what I do and how I get it:

    Running tests on Windows 10 VM - host is Xubuntu 16.04. Latest version of Edge and Edge driver and Selenium 3.3.0 javascript binding, testing ReactJs app.

    The test is doing the following: It starts on a login page, where it enters different values for the username and password fields. And waits for an error message to be dispalyed. That runs a couple of times with different values and looking for different messages after the Login button has been clicked. Then it enters the correct values and logs in, logs out and starts again. So the page has simply a few funcitons click() - fields and login button, sendKeys() - to enter values and wait() - to wait for the messages. However, it fails to click the Login button after a few times. Or more likely it counts it as if it clicks it but nothing happens because it moves on to waiting for the error message, where it fails. I know it has not reacted to the click and the problem is not the message because the click of the Login disables the button and fields. And this behaiour does not happen while waiting for the message. After it has '’clicked’’.

    If I manually interfere with the test every now and then by clicking the Login button when it gets stuck like that, it passes. Also runs fine on Firefox, Chrome, IE11.

  • Hi Viktoria,

    I appreciate you providing this detailed information.  It clarifies the problem area and also shows that the issue is not binding language dependent.

    I will create a WebDriver test to track any missed click events and delays between them.

    Thanks again for the very helpful information and please send any other comments you may have,


  • Microsoft Edge Team

    Changed Assigned To to “Mike J.”

    Changed Assigned To from “Mike J.” to “John J.”

    Changed Status to “Confirmed”

    Changed Title from “Selenium click sometimes not working using Edge driver” to “Selenium click sometimes not working using Edge driver”

    Changed Status from “Confirmed” to “Not reproducible”

  • Hey there, were you by chance on a high dpi machine? We recently had a fix go in that takes into account zoom when using click() which may have fixed this as I’m not able to repro. It’s clicking both examples I found in the bug. Also what version of Windows 10 / WebDriver are you using? You can find your build of windows by running winver and the build of webdriver by right-clicking the .exe and going to details, it’s the full version number.

  • Hi I’ve tested again and the issue is still here.

    I’ve cleaned my code to be 100% webdriver api compliant.

    I’ve added notes in the to run the test.
    I’ve tested with EdgeDriver Release 15063


You need to sign in to your Microsoft account to add a comment.

Sign in