By Maria

2017-07-04 18:26:14 8 Comments

I used explicit waits and I have the warning:

org.openqa.selenium.WebDriverException: Element is not clickable at point (36, 72). Other element would receive the click: ... Command duration or timeout: 393 milliseconds

If I use Thread.sleep(2000) I don't receive any warnings.

@Test(dataProvider = "menuData")
public void Main(String btnMenu, String TitleResultPage, String Text) throws InterruptedException {
    WebDriverWait wait = new WebDriverWait(driver, 10);

    try {
    } catch (Exception e) {
    Assert.assertEquals(driver.findElement(By.cssSelector(TitleResultPage)).getText(), Text);


@DebanjanB 2017-07-05 03:16:31

WebDriverException: Element is not clickable at point (x, y)

This is a typical org.openqa.selenium.WebDriverException which extends java.lang.RuntimeException.

The fields of this exception are :

  • BASE_SUPPORT_URL : protected static final java.lang.String BASE_SUPPORT_URL
  • DRIVER_INFO : public static final java.lang.String DRIVER_INFO
  • SESSION_ID : public static final java.lang.String SESSION_ID

About your individual usecase, the error tells it all :

WebDriverException: Element is not clickable at point (x, y). Other element would receive the click 

It is clear from your code block that you have defined the wait as WebDriverWait wait = new WebDriverWait(driver, 10); but you are calling the click() method on the element before the ExplicitWait comes into play as in until(ExpectedConditions.elementToBeClickable).


The error Element is not clickable at point (x, y) can arise from different factors. You can address them by either of the following procedures:

1. Element not getting clicked due to JavaScript or AJAX calls present

Try to use Actions Class:

WebElement element = driver.findElement("navigationPageButton"));
Actions actions = new Actions(driver);

2. Element not getting clicked as it is not within Viewport

Try to use JavascriptExecutor to bring the element within the Viewport:

WebElement myelement = driver.findElement("navigationPageButton"));
JavascriptExecutor jse2 = (JavascriptExecutor)driver;
jse2.executeScript("arguments[0].scrollIntoView()", myelement); 

3. The page is getting refreshed before the element gets clickable.

In this case induce ExplicitWait i.e WebDriverWait as mentioned in point 4.

4. Element is present in the DOM but not clickable.

In this case induce ExplicitWait with ExpectedConditions set to elementToBeClickable for the element to be clickable:

WebDriverWait wait2 = new WebDriverWait(driver, 10);

5. Element is present but having temporary Overlay.

In this case induce ExplicitWait with ExpectedConditions set to invisibilityOfElementLocated for the Overlay to be invisible.

WebDriverWait wait3 = new WebDriverWait(driver, 10);

6. Element is present but having permanent Overlay.

Use JavascriptExecutor to send the click directly on the element.

WebElement ele = driver.findElement(By.xpath("element_xpath"));
JavascriptExecutor executor = (JavascriptExecutor)driver;
executor.executeScript("arguments[0].click();", ele);

@TaylorTheDeveloper 2018-05-15 20:25:28

To #6/#2 above: The .ExecuteScript method is now accessible from the web driver itself rather than the JavascriptExecutor. Thanks for the well written answer!

@Rajagopalan 2018-08-07 07:59:33

You have covered many possibilities in which only 5 and 6 are correct way to handle the mentioned error. The first four throws different error for which the solution you gave won't work. For an example point number 3 is actually a stale element problem that wouldn't work even though how long you wait with elementToBeClickble method. That has to be handled differently.

@rescdsk 2018-07-03 22:09:59

I ran into this error while trying to click some element (or its overlay, I didn't care), and the other answers didn't work for me. I fixed it by using the elementFromPoint DOM API to find the element that Selenium wanted me to click on instead:

element_i_care_about = something()
loc = element_i_care_about.location
element_to_click = driver.execute_script(
    "return document.elementFromPoint(arguments[0], arguments[1]);",

I've also had situations where an element was moving, for example because an element above it on the page was doing an animated expand or collapse. In that case, this Expected Condition class helped. You give it the elements that are animated, not the ones you want to click. This version only works for jQuery animations.

class elements_not_to_be_animated(object):
    def __init__(self, locator):
        self.locator = locator

    def __call__(self, driver):
            elements = EC._find_elements(driver, self.locator)
            # :animated is an artificial jQuery selector for things that are
            # currently animated by jQuery.
            return driver.execute_script(
                'return !jQuery(arguments[0]).filter(":animated").length;',
        except StaleElementReferenceException:
            return False

@Sudheesh.M.S 2018-08-01 05:01:49

Scrolling the page to the near by point mentioned in the exception did the trick for me. Below is code snippet:

$wd_host = 'http://localhost:4444/wd/hub';
$capabilities =
        \WebDriverCapabilityType::BROWSER_NAME => 'chrome',
        \WebDriverCapabilityType::PROXY => [
            'proxyType' => 'manual',
            'httpProxy' => PROXY_DOMAIN.':'.PROXY_PORT,
            'sslProxy' => PROXY_DOMAIN.':'.PROXY_PORT,
            'noProxy' =>  PROXY_EXCEPTION // to run locally
$webDriver = \RemoteWebDriver::create($wd_host, $capabilities, 250000, 250000);
// Wait for 3 seconds
// Scrolls the page vertically by 70 pixels 
$webDriver->executeScript("window.scrollTo(0, 70);");

NOTE: I use Facebook php webdriver

@Rester Test 2018-04-13 09:25:04

In case you need to use it with Javascript

We can use arguments[0].click() to simulate click operation.

var element = element(by.linkText('webdriverjs'));

@Fisk 2018-06-01 10:48:02

Works! I cannot imagine way it works, but otherwise it clicks on overlay layer (waiting of overlay closing by 'invisibilityOfElementLocated' takes about 30sec.).

@Chaudhry Waqas 2018-10-22 19:36:09

thanks man, you saved my time.

@fg78nc 2017-07-04 18:39:25

You can try

WebElement navigationPageButton = (new WebDriverWait(driver, 10))

@Maria 2017-07-04 18:53:01

It is not help me.

@fg78nc 2017-07-04 18:55:09

Are you getting same error?

@Maria 2017-07-04 18:57:16

Yes: org.openqa.selenium.WebDriverException: Element is not clickable at point (36, 72). Other element would receive the click: <div tabindex="0" class="waiter-ui-lock"></div> Command duration or timeout: 70 milliseconds

@fg78nc 2017-07-04 18:59:33

try the following WebElement element = driver.findElement("navigationPageButton")); Actions actions = new Actions(driver); actions.moveToElement(element).click().perform();

@Maria 2017-07-04 19:03:50

It is not help too. I have two Exception and one AssertionError and next some error "Element is not clickable at point "

@fg78nc 2017-07-04 19:04:42

Are you sure page is not refreshing at the time you are trying to click?

@Maria 2017-07-04 19:09:44

A pop-up menu appears on the page but the page itself is not updated

@fg78nc 2017-07-04 19:22:38

Maybe you now operate on pop-up window instead?

@Maria 2017-07-04 19:24:32

If i using Thread.Sleep then all work. But i using Wait all fail.

@try-catch-finally 2017-07-04 20:12:05

presenceOfElementLocated() is not enough, the element has been located. The error message would be different if the element cannot be located. The error says the element is not visible or something overlays that element.

@pburgr 2018-05-30 14:16:08

I have the same problem, after a modal dialog is opened, I'm not able to click element inside the dialog. Have already tried all suggestions from this thread, nothing worked. I can identify the overlaying frame, but cannot switch to the frame, getting NoSuchFrameException.

@fg78nc 2018-05-30 22:42:34

@pburgr How do you switch to the frame?

@pburgr 2018-05-31 07:04:13

with this I'm getting NoSuchFrameException: WebElement languageModal = driver.findElement("languageModal")); driver.switchTo().frame(languageModal); but WebElement languageModal = driver.findElement("languageModal"));; is OK, no exception at all.

@fg78nc 2018-05-31 13:22:27

@pburgr Are you able to locate frame through id in browser console?

Related Questions

Sponsored Content

44 Answered Questions

[SOLVED] Debugging "Element is not clickable at point" error

3 Answered Questions

[SOLVED] Selenium Webdriver (Java) cannot click the AJAX button

3 Answered Questions

0 Answered Questions

1 Answered Questions

1 Answered Questions

3 Answered Questions

[SOLVED] Element is not clickable at point using chrome driver

Sponsored Content