The element cannot be clicked at this point as another element would intercept the click:

Question

The element cannot be clicked at this point as another element would intercept the click:

Having an issue with clicking a button at the top of the page. The CSS selector works fine in my local Eclipse environment, but when trying to run it on Jenkins server on my local machine, it fails with an error stating that the element is not clickable. The screenshot from the failed test on Jenkins shows that the header is overlapping the button that needs to be clicked. I have tried various solutions using XPath, CSS, moving to the element, and moving the mouse, but nothing seems to work. Any assistance would be greatly appreciated.

I'm attempting to click on the 'Add' button.

org.openqa.selenium.WebDriverException: Element is not clickable at point (775.25, 10.166671752929688). Other element would receive the click: <div class="globalHeader-UtilTop"></div>
Command duration or timeout: 69 milliseconds
Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46'
System info: host', ip: '', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_80'

<div class="Componet-intels**strong text**-Container">
<div class="Componet-intels-Container-Header">
<div class="Componet-intels-Container-Content">
<div class="Componet-intels-Container-Content-Row">
<span class="Componet-intels-Item"> Item # </span>
<span class="Componet-intels-Text-Item">
<span class="Componet-intels-Lable-Quantity"> Qty: </span>
<span class="Componet-intels-Text-Quantity">
<span class="Componet-intels-Button">
**<input class="Componet-intelsButtonIcon" type="button" value="Add">**
</span>
</div>

java css selenium jenkins cucumber

Answer 1

Answer №1

Issue: Unable to click on element at coordinates (775.25, 10.166671752929688). Another element is intercepting the click.

The problem seems to be that the desired element is being obscured by a different div element, causing it not to be clickable.

Possible solutions could involve adjusting the UI layout so that the header does not hide the target element. Alternatively, you can try the following steps:

Attempt maximizing the browser window using WebDriver to check if the header no longer obstructs the element
```
driver.manage().window().maximize() 
```

Utilize JavaScript for clicking on the element

WebElement element = driver.findElement(By.<locator>);
JavascriptExecutor executor = (JavascriptExecutor)driver;
executor.executeScript("arguments[0].click()", element)`

Answer 2

Issue: Unable to click on element at coordinates (775.25, 10.166671752929688). Another element is intercepting the click.

The problem seems to be that the desired element is being obscured by a different div element, causing it not to be clickable.

Possible solutions could involve adjusting the UI layout so that the header does not hide the target element. Alternatively, you can try the following steps:

Attempt maximizing the browser window using WebDriver to check if the header no longer obstructs the element
```
driver.manage().window().maximize() 
```

Utilize JavaScript for clicking on the element

WebElement element = driver.findElement(By.<locator>);
JavascriptExecutor executor = (JavascriptExecutor)driver;
executor.executeScript("arguments[0].click()", element)`

Answer 3

Answer №2

Implement JavascriptExecutor for your automation task:

Locate the element using driver.findElement(By.<locator>);

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

Answer 4

Implement JavascriptExecutor for your automation task:

Locate the element using driver.findElement(By.<locator>);

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

Answer 5

Answer №3

In my particular situation, I encountered a scenario where I needed to interact with a button that only became visible after several graphs had loaded along with an ajax image. To resolve this issue, I followed the steps below:

Firstly, locate the xpath/css element that disappears upon completion of the ajax call and explicitly wait for it to become invisible using
```
wait.until(ExpectedConditions.invisibilityOf(element));
```
Next, add another explicit wait for the button to be clickable by using
```
wait.until(ExpectedConditions.elementToBeClickable(element));
```

Finally, utilize JavaScript to simulate clicking on the button-

WebElement element = driver.findElement(By.xpath(""));
JavascriptExecutor js = (JavascriptExecutor)driver;<br>
js.executeScript("arguments[0].click()", element);

If these steps do not yield the desired result, consider inserting an implicit wait between step 1 and 2.

Answer 6

In my particular situation, I encountered a scenario where I needed to interact with a button that only became visible after several graphs had loaded along with an ajax image. To resolve this issue, I followed the steps below:

Firstly, locate the xpath/css element that disappears upon completion of the ajax call and explicitly wait for it to become invisible using
```
wait.until(ExpectedConditions.invisibilityOf(element));
```
Next, add another explicit wait for the button to be clickable by using
```
wait.until(ExpectedConditions.elementToBeClickable(element));
```

Finally, utilize JavaScript to simulate clicking on the button-

WebElement element = driver.findElement(By.xpath(""));
JavascriptExecutor js = (JavascriptExecutor)driver;<br>
js.executeScript("arguments[0].click()", element);

If these steps do not yield the desired result, consider inserting an implicit wait between step 1 and 2.

Answer 7

Answer №4

During my Salesforce automation with Robot Framework and Chrome browser, I encountered an error that was causing inconvenience. Fortunately, the issue was resolved by utilizing the key press event method using (Press Keys ${locator} RETURN) as a replacement for the 'Click Element' or 'Click Button' keywords.

Answer 8

During my Salesforce automation with Robot Framework and Chrome browser, I encountered an error that was causing inconvenience. Fortunately, the issue was resolved by utilizing the key press event method using (Press Keys ${locator} RETURN) as a replacement for the 'Click Element' or 'Click Button' keywords.

The element cannot be clicked at this point as another element would intercept the click:

Answer №1

Answer №2

Answer №3

Answer №4

Similar questions

JPQL Query Fails to Sort Results Using ORDER BY

Using Selenium to automate pressing the login button on Discord

Oops! Looks like we have encountered an issue with reading the property 'checked' of nothing

What is the best way to mark a MenuItem as active within a Material UI Drawer component?

"Enhancing the aesthetics: Stylish blue borders around Bootstrap

Using gradients in the app bar with ReactJS and Material UI is not currently supported

The custom CSS styling is triggered only when the page is resized in Bootstrap

javascript alter css property display to either visible or hidden

What is the best way to prevent the child elements from inheriting the hover effect of the main container?

Issue with the react-native-autocomplete-input where the list does not close after selecting an option

Using Javascript to Trigger Events on Selection

What strategies can I use to locate elements containing specific strings within an id using selenium?

In Laravel Blade, you can dynamically add rows and columns based on a certain condition

Using WebDriver to select a checkbox based on the value within a span element

The dropdown menu is unable to open directly below the main menu item

How to show a tooltip inline by utilizing CSS styling

Retrieve data from a webpage without the need for parsing using Json AsyncTask

Floating footers with centered content - they remain aligned in the center even when zoomed out

Experiencing a Stack Overflow Error while attempting to log using log4j

Locate the table cell that contains certain text, then identify its surrounding elements such as parent elements and