I am getting error "Web element was found but not clickable"
I am getting error "Web element was found but not clickable"
Description:
The most probable reasons for getting the "Web element was found but not clickable" error message are:
- The user is not replicating correct behavior through blocks in the automation flow.
- The element is there in HTML DOM but not available for interaction, e.g. the browser is still loading or it may be hidden (not visible).
- The element is clickable but there is a spinner/overlay on top of it.
Let's try to understand the first issue by an example in Leapwork:
- User opens amazon.com and captures "Echo & Alexa" from the "Departments" drop-down (without hovering/expanding the department).
- Run test.
- The above test will fail with the "Web element was found but not clickable" error message.
Please observe that the test started and amazon.com was opened, but the user did not add a block for hovering on the "Departments" drop-down to expand it, and still tried to click on the "Echo & Alexa" link, which was hidden in HTML. So, the element was there in the HTML structure but it was not clickable as the drop-down was not expanded.
Please try to look at the studio.log file to get more details about the error message. The path of log files is: C:\Program Files\Leapwork\Logs\studio.log.
Resolution:
Below are the ways to handle the above-mentioned scenarios:
Scenario 1:
User is not replicating correct behavior through blocks in the automation flow.
Resolution 1:
To solve this, the user should try to replicate the behavior in the flow as a manual tester would do. Example shown below:
Scenario 2:
The element is there in HTML DOM but not available for interaction, e.g. the browser is still loading or it may be hidden (not visible).
Resolution 2:
In this situation, elements usually take time to load properly. The user should use the "Await DOM change" feature in blocks to handle this synchronization challenge.
Scenario 3:
The element is clickable but there is a spinner/overlay on top of it.
Resolution 3:
Check the condition; if a spinner/overlay is displayed, then wait. Else move ahead (click Await not found checkbox) and then use the click web element block.
For any clarification, please contact our Priority Support.