ElementNotInteractableException: element not interactable: element has zero size appears since upgrade to chromedriver 83

Question

I use the following docker image to run my cucumber tests:

https://hub.docker.com/r/selenium/standalone-chrome/

Unfortunately, starting from today it seems that whenever I run my tests I get the errors below. They appear at the start of each test. It does not matter what I do on the page.

**13:38:26 [exec] org.openqa.selenium.ElementNotInteractableException: element not interactable: element has zero size

13:38:26 [exec] (Session info: chrome=83.0.4103.61)**

I did some digging and I noticed the chromedriver version was updated from 81 to 83. I managed to fix this issue by using an older docker image from that docker hub link which has chromedriver 81. But if I attempt to use chromedriver 83 again it will not work.

Has anyone else encountered this? Is there a new chrome option I need to add because of the update?

Have you solved this issue yet? I’m seeing the same thing. — Gordon Isnor, May 26 '20 at 17:24
Nope. I had to put everything on hold for something more urgent. But I managed to make it work by reverting to Chrome 81 + chromedriver 81. I'll try some more — Robert Curetean, May 27 '20 at 19:09
Same issue here, tests ran fine in Chrome 81 but getting the same error you are in 83. — yaryar123, May 30 '20 at 03:00

score 22 · Accepted Answer · edited Nov 21 '20 at 11:32

The root cause of that issue is that Chrome doesn't scroll to the element outside of the viewport. Instead of it, Chrome tries to click on it outside of the viewing area. That's why the issue appears. It is definitely an issue with Chrome 83 because I didn't face it on Chrome 81.

Moreover, I have no such issue on Windows machine, it reproduced only on Linux (I'm using selenoid docker images).

Solution with a click via JS is not the best option, because via JS you can click anywhere even for unclickable elements (e.g. overlapped by other objects). It's an unsafe operation.

Instead of this, I would suggest scrolling to the element before click and after native click(); it will work just perfectly.

JavascriptExecutor executor = (JavascriptExecutor) driver;
executor.executeScript("arguments[0].scrollIntoView(true);", element);    
element.click();

this answer is great, but instead of scrolling using javascript, you can use selenium "move_to_element" option like this: from selenium.webdriver.common.action_chains import ActionChains ActionChains(driver).move_to_element(element).perform() element.click() — Avishay116, Jun 15 '20 at 12:04

Wael.B · Answer 2 · 2020-05-27T17:13:48.880

7

I'm getting this error also, i did some digging, i found that the element size contains 0, for example an element of size 200 x 0 will get you this error if you want to click on it. This is not a docker only error, i'm getting it on local chrome 83.

Try clicking on element using the Javascript Executor:

JavascriptExecutor executor = (JavascriptExecutor) driver;
executor.executeScript("arguments[0].click();", element);

edited May 27 '20 at 17:13

answered May 27 '20 at 17:00

Wael.B

71
3

This seems to work, but I need to add this in almost each cucumber step. I'll come back to this solution if everything else fails. – Robert Curetean May 27 '20 at 19:13
1

this solution works for me, thanks! fwiw, i'm on chrome 83, ruby, rspec, running headless on our CI server. Replaced element.click with calls to this method: def click_link(element) execute_script("arguments[0].click();", element) end – TimCO May 28 '20 at 15:22

score 6 · Answer 3 · answered May 26 '20 at 18:44

6

I got around this by using the --window-size argument when I'm using headless chrome. E.g. chrome --headless --window-size=400,800.

I do not know what changed or why this is a sufficient workaround.

answered May 26 '20 at 18:44

John

69
1

1

Unfortunately, I already have the --window-size argument and it still does not work. I cannot switch to headless because it will cause all my download tests to stop working. – Robert Curetean May 27 '20 at 19:11

score 4 · Answer 4 · answered Jun 22 '20 at 15:45

In our case, the root cause was a CSS/HTML problem: an anchor was wrapping a div and expected to implicitly gain a size from that of this child element.

Previous versions of Chrome had been tolerant of this, but from v.83 Chrome seems to have become stricter on this front.

So, in this case the solution was to change from something like this:

<a href="http://example.org">
  <div class="class with style giving height and width">
    some content
  </div>
</a>

To something like this:

<a href="http://example.org" class="class with style giving height and width">
  some content
</a>

This is valid HTML5.

Thanks, this is a better approach IMO than having to do hacky JS on the test side. Investigating the DOM first led me to solve the problem more elegantly than throwing in JS executor. — k_rollo, Oct 21 '21 at 07:19

score 3 · Answer 5 · answered Jun 24 '20 at 21:14

I ended up using scrollIntoView() which did the trick (below code is from Protractor test):

// scroll to it
browser.executeScript('document.getElementById("targetID").scrollIntoView()');

browser.sleep(500);

// click it
element(by.id('targetID')).click();

score 1 · Answer 6 · answered Jun 16 '20 at 08:09

1

I got around it by clicking a child <input> element inside the element that supposedly had zero width.

answered Jun 16 '20 at 08:09

Marcel van der Drift

373
3
5

Using accepted answer alone didn't work for me. I was trying to click on a
element, clicked on the child instead and it worked.

Laurent

Aug 04 '22 at 01:32

score 0 · Answer 7 · answered May 29 '20 at 14:34

I had the same problem as you with chrome driver updating to 83, i was able to get around this problem.

 WebDriverWait wait = new WebDriverWait(this.Driver, TimeSpan.FromSeconds(10));
            var result = wait.Until(SeleniumExtras.WaitHelpers.ExpectedConditions.ElementToBeClickable(By.CssSelector(".btnSaveChanges")));
            ExcuteJquery("$j(\".btnSaveChanges div:contains('" + Text + "')\").click()");

Using Jquery will help you access this

This code isn't runnable. Fix the typos and indents. – Grant Birchmeier May 06 '21 at 20:46 — Grant Birchmeier, May 06 '21 at 20:46

score 0 · Answer 8 · answered Aug 17 '21 at 12:25

0

Original post: https://stackoverflow.com/a/68740025/1244630

Instead of using Click, rather press enter. This worked for me:

IWebDriver driver = ...;
var button = driver.FindEment(...);
button.SendKeys(Keys.Enter);

answered Aug 17 '21 at 12:25

Pooven

1,744
1
25
44

Janek · Answer 9 · 2021-09-21T13:25:32.210

0

My solution:

    Actions actions = new Actions(driver);
    actions.moveToElement(element);
    actions.perform();

Documentation: https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/interactions/Actions.html

edited Sep 21 '21 at 13:25

answered Sep 20 '21 at 10:40

Janek

25
7

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-ask). – Community Sep 20 '21 at 12:38

score 0 · Answer 10 · answered Apr 11 '23 at 12:14

0

I have also face this issue, I replace the identifier by XPATH.Why don't you try it

answered Apr 11 '23 at 12:14

Muhammad Yasar

1

ElementNotInteractableException: element not interactable: element has zero size appears since upgrade to chromedriver 83

10 Answers10

Linked