Selenium - Element is not clickable at point

Question

I am using selenium for test script. I am getting following error and this error randomly occur. When I run 10 times, I get this about twice. So it's not really reproducible. Does anyone know why this is happening? the element I am trying to click is definitely visible in the browser and doesn't move around so there is no need to resize or drag element. I am using chrome webdriver and I read other troubleshooting strategies (Debugging "Element is not clickable at point" error) and they don't seem relevant to my issue. I waited enough time as well.

UnknownError: unknown error: Element is not clickable at point (167, 403). Other element would receive the click: <div class="leftMasterBackground"></div>

Can you give us some information about what Element you want to click? It would also be interesting what elements surround it and what actions are performed before the click. — Tobias Kloss
– Tobias Kloss, Commented Apr 8, 2015 at 7:30
Have all scripts and styles on the page finished loading when this error occurs? — FDM
– FDM, Commented Apr 8, 2015 at 7:56
The element gets loaded when the page is loaded so technically, there should be no waiting time required to check existence of the element(checking this element happened after a few tests of others) I checked the screenshot that was taken when the page was loaded, I could visually see the element loaded on the page so there is no reason why selenium could not detect the element. What I am trying to do is to click the element(button). It's very odd and annoying as it happens randomly. Does anyone know where about of the element selenium clicks? — haeminish
– haeminish, Commented Apr 9, 2015 at 0:14

Johnny · Accepted Answer · 2016-11-23 10:30:16Z

7

There are a number of steps you can do in order to improve the stability while clicking on different UI elements:

Explicitly wait for it's presence in the DOM
Scroll into the element view
Check if clickable

Does it helped the stability?

WebDriverWait wait = new WebDriverWait(driver, 3)
JavascriptExecutor js = ((JavascriptExecutor) driver)

//presence in DOM
wait.until(ExpectedConditions.presenceOfElement(By.id("ID")));

//scrolling
WebElement element = driver.findElement(By.id("ID")));  
js.executeScript("arguments[0].scrollIntoView(true);", element);

//clickable
wait.until(ExpectedConditions.elementToBeClickable(By.id("ID")));

Further, if you will decide to override the default Actions interface with more customized one, you can use two type of clicks (for example): click() which will have all those stability steps and fastClick() which will be the default clicking without any varification.

edited Nov 23, 2016 at 10:30

answered Apr 9, 2015 at 11:05

Johnny

15.6k15 gold badges85 silver badges120 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

JCC Over a year ago

I only used the //scrolling block with my issue and it worked. Thanks. There's probably a more DRY solution in making this a function to call repeatedly all over your protractor tests. I'm sure there are many places where you need to scroll to a certain spot on the page in order to click.

Johnny Over a year ago

@JCC in our solution, those native selenium libraries wrapped in additional abstraction level. So we have methods like: element.scrollToElement().click(), element.waitUntilPresence().click() and etc.

alansiqueira27 Over a year ago

fantastic job! The key thing is to SCROLL!

Benjamin Loison · Accepted Answer · 2023-12-29 14:05:11Z

3

I have solved by catching the exception and managing it like this:

WebDriver driver = new ChromeDriver();
WebElement element = driver.findElement(By.id("ID"));
boolean clicked = false;
do{
    try {
        element.click();
    } catch (WebDriverException e) {
        continue;
    } finally {
        clicked = true;
    }
} while (!clicked);

edited Dec 29, 2023 at 14:05

Benjamin Loison

5,7504 gold badges20 silver badges37 bronze badges

answered Feb 11, 2016 at 10:53

billi90

456 bronze badges

3 Comments

Lee Goddard Over a year ago

Have a look at ExpectedConditions.isClickable()

billi90 Over a year ago

I've already seen this functionality, but it doesn't work well with chromedriver. What happen is: the condition return true, but the element isn't effectively clickable.

Lee Goddard Over a year ago

I had this error, which brought me to this page. Is your element covered by another (transparent) element? Is it animated? Is it possible to inject JS with .executeScript (or your binding's equivalent) to click the element?

Paul Roub · Accepted Answer · 2016-04-19 19:40:13Z

2

I was also facing same problem with Chrome. I have solved that putting one line of code before clicking on the element:

scrollToViewElement(driver,xpath);

edited Apr 19, 2016 at 19:40

Paul Roub

36.5k27 gold badges88 silver badges95 bronze badges

answered Apr 19, 2016 at 19:36

user6226795

211 bronze badge

Comments

Benjamin Loison · Accepted Answer · 2024-02-14 23:08:17Z

2

For best solution, use JavaScript to focus element. Using:

JavascriptExecutor jsnew = (JavascriptExecutor)driver;
WebElement element = driver.findElement(By.xpath(""));
jsnew.executeScript("arguments[0].scrollIntoView({block:\"center\"});", element);

In place of xpath you can use id, css selector: This scrollIntoView will bring the this specific element in middle of page, then driver will be able to hit element.

If it is normal button or link, use jsnew.executeScript("arguments[0].click();", element);

This is consistent solution for click.

edited Feb 14, 2024 at 23:08

Benjamin Loison

5,7504 gold badges20 silver badges37 bronze badges

answered Oct 11, 2019 at 10:08

Siddiqui Arshad

312 bronze badges

Comments

Benjamin Loison · Accepted Answer · 2024-02-14 23:08:35Z

1

Click parent element of the element which you want to click. This can be workaround solution only.

edited Feb 14, 2024 at 23:08

Benjamin Loison

5,7504 gold badges20 silver badges37 bronze badges

answered Mar 18, 2016 at 7:09

Balu

116 bronze badges

Comments

dimyo · Accepted Answer · 2017-08-01 16:30:06Z

0

I got the same issue due to one of spinner was hiding the element.

I gave xpath and it resolved the issue. Other people suggested to 1. scroll 2. sleep also worked for them.

answered Aug 1, 2017 at 16:30

dimyo

1331 silver badge10 bronze badges

1 Comment

dimyo Over a year ago

you can also solve the following error using wait condition: waitUntilTrueOrTimeout(ExpectedConditions.invisibilityOfElementLocated(elementHidingOtherElement)); protected <V> V waitUntilTrueOrTimeout(final ExpectedCondition<V> isTrue) { return waitUntilTrueOrTimeout(isTrue, waitTimeOutSeconds); } protected <V> V waitUntilTrueOrTimeout(final ExpectedCondition<V> isTrue, final int waitTimeSeconds) { return new WebDriverWait(this.driver, waitTimeSeconds).ignoring(StaleElementReferenceException.class).until(isTrue);

Mate Mrše · Accepted Answer · 2018-10-05 09:41:45Z

0

This happens only on chrome so it works on ie and firefox
ChromeDriver always clicks the middle of the element
The reason Chrome driver doesn't calculate the correct screen location of link.

Solution:

// Find an element and define it

WebElement elementToClick = driver.findElement(By.xpath("some xpath"));
// Scroll the browser to the element's Y position
((JavascriptExecutor) driver).executeScript("window.scrollTo(0,"+elementToClick.getLocation().y+")");
// Click the element
elementToClick.click();

edited Oct 5, 2018 at 9:41

Mate Mrše

8,52413 gold badges52 silver badges95 bronze badges

answered May 2, 2017 at 6:23

Manan Trivedi

11 bronze badge

Collectives™ on Stack Overflow

Selenium - Element is not clickable at point

7 Answers 7

3 Comments

3 Comments

Comments

Comments

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

3 Comments

3 Comments

Comments

Comments

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related