Selenium-Debugging: Element is not clickable at point (X,Y)

Question

I try to scrape this site by Selenium.

I want to click in "Next Page" buttom, for this I do:

driver.find_element_by_class_name('pagination-r').click()

it works for many pages but not for all, I got this error

WebDriverException: Message: Element is not clickable at point (918, 13). Other element would receive the click: <div class="linkAuchan"></div>

always for this page

I read this question

and I tried this

driver.implicitly_wait(10)
el = driver.find_element_by_class_name('pagination-r')
action = webdriver.common.action_chains.ActionChains(driver)
action.move_to_element_with_offset(el, 918, 13)
action.click()
action.perform()

but I got the same error

When I go to that page there is no element with the class name, `pagination-r` or `linkAuchan`. I guess the page has changed? — JeffC, Jun 30 '16 at 01:57

RemcoW · Accepted Answer · 2019-10-09T07:39:41.763

199

Another element is covering the element you are trying to click. You could use execute_script() to click on this.

element = driver.find_element_by_class_name('pagination-r')
driver.execute_script("arguments[0].click();", element)

edited Oct 09 '19 at 07:39

answered Jun 17 '16 at 11:21

RemcoW

4,196
1
22
37

6

@RemcoW what is the meaning of `arguments[0]` here? – CKM Apr 30 '18 at 06:02
20

@chandresh The `execute_script()` method has 2 parameters. The first is the script, the second is a vararg in which you can place any parameters used in the script. In this case we only need the element as parameter, but since it is a vararg our element is the first in the collection. For example you could also do `driver.execute_script("arguments[0].click(); arguments[1].click();" element1, element2)` This would click both elements passed – RemcoW Apr 30 '18 at 10:01
3

Bear in mind, if you are writing tests that intend to use the website like a real user you are potentially doing something that a real user cannot do because the element they want to click on is covered. Don't do this to just make your tests pass! – Ardesco Mar 13 '19 at 16:31
@CKM driver.execute_script("arguments[0].click();", element) - `arguments[0]` is `element`. You can do driver.execute_script("arguments[0].click();doSmthElse(arguments[1])", element, doSmthElseParam) and in this case `arguments[1]` would be `doSmthElseParam` – hipokito Feb 24 '21 at 12:24

score 28 · Answer 2 · answered Jan 26 '21 at 01:56

28

Because element is not visible on the browser, first you need to scroll down to the element this can be performed by executing javascript.

element = driver.find_element_by_class_name('pagination-r')
driver.execute_script("arguments[0].scrollIntoView();", element)
driver.execute_script("arguments[0].click();", element)

answered Jan 26 '21 at 01:56

Smart Dev

381
3
2

6

`arguments[0].scrollIntoView();` is crucially missing from the currently accepted answer. This works perfectly. – Lawrence Mar 18 '21 at 22:27
1

arguments[0].scrollIntoView() is crucial INDEED!!! This made my day, and helped me so much in 2022. Thank you, – data_runner May 16 '22 at 11:31
1

driver.execute_script("arguments[0].scrollIntoView();", element) thank you so much about this – lam vu Nguyen Nov 11 '22 at 14:14

score 18 · Answer 3 · edited Jun 21 '23 at 21:40

18

I had a similar issue where using ActionChains was not solving my error: WebDriverException: Message: unknown error: Element is not clickable at point (5 74, 892)

I found a nice solution if you dont want to use execute_script:

from selenium.webdriver.common.keys import Keys #need to send keystrokes

inputElement = self.driver.find_element_by_name('checkout')

inputElement.send_keys("\n") #send enter for links, buttons

or

inputElement.send_keys(Keys.SPACE) #for checkbox etc

edited Jun 21 '23 at 21:40

Benjamin Loison

3,782
4
16
33

answered Oct 17 '17 at 08:04

Deepak Garud

977
10
18

can we click too after sending keys?? – Abhishek Gupta Sep 25 '18 at 12:57
@AbhishekGupta - The idea is that we can use keystrokes to simulate the action like link click or button click etc. - Instead of using the mouse. What is your scenario where you need both? – Deepak Garud Oct 01 '18 at 14:46
1

Everything else was not working in my case (a checkbox). Sending Keys.SPACE worked like as magic. – ePandit Apr 29 '20 at 08:19

Chetan Kolhe · Answer 4 · 2020-06-13T11:02:49.467

I have written logic to handle these type of exception .

   def find_element_click(self, by, expression, search_window=None, timeout=32, ignore_exception=None,
                       poll_frequency=4):
    """It find the element and click then  handle all type of exception during click

    :param poll_frequency:
    :param by:
    :param expression:
    :param timeout:
    :param ignore_exception:list It is a list of exception which is need to ignore.
    :return:
    """
    if ignore_exception is None:
        ignore_exception = []

    ignore_exception.append(NoSuchElementException)
    if search_window is None:
        search_window = self.driver

    end_time = time.time() + timeout
    while True:
        try:
            web_element = search_window.find_element(by=by, value=expression)
            web_element.click()
            return True
        except tuple(ignore_exception) as e:
            self.logger.debug(str(e))
            if time.time() > end_time:
                self.logger.exception(e)
                time.sleep(poll_frequency)
                break
        except Exception as e:
            raise
    return False

It is more efficient than other available option . Us ElementClickInterceptedException in ignore_exception list . — Chetan Kolhe, May 30 '20 at 08:07
very good solution! I have added ElementClickInterceptedException and ElementNotInteractableException in the ignore_exception, set timeout to 3 seconds, and works like a charm. — nejcb1, Jun 12 '20 at 06:02

score 1 · Answer 5 · edited Feb 27 '20 at 05:05

1

If you are receiving an element not clickable error, even after using wait on the element, try one of these workarounds:

Use Action to move to the location of element and then run perform on action

WebElement element = driver.findElement(By("element_path"));
Actions actions = new Actions(driver);
actions.moveToElement(element).click().perform();`

Check for an overlay or spinner on the element and wait for its invisibility

By spinnerimg = By.id("spinner ID");
WebDriverWait wait = new WebDriverWait(driver, timeOutInSeconds);
wait.until(ExpectedConditions.invisibilityOfElementLocated(spinnerimg ));

Hope this helps

edited Feb 27 '20 at 05:05

Z4-tier

7,287
3
26
42

answered Feb 27 '20 at 02:12

quickauto

11
2

you can use markdown to format the code in your answer, which enhances readability. For example: `WebElement element = driver.findElement(By("element_path")); ` Just wrap the code with the backtick character: ` – Paul Degnan Feb 27 '20 at 03:00

score 0 · Answer 6 · edited Jun 21 '23 at 21:40

0

Use explicit wait instead of implicit.

new WebDriverWait(TestingSession.Browser.WebDriver, TimeSpan.FromSeconds(10)).Until(ExpectedConditions.ElementExists((By.ClassName("pagination-r'"))));

edited Jun 21 '23 at 21:40

Benjamin Loison

3,782
4
16
33

answered Jun 17 '16 at 12:30

Rakesh Raut

183
3
12

6

Can you rewrite it in python please – parik Jun 17 '16 at 12:50
1

Sorry dude. I never worked on python, though you can get help on explicit waits in python. – Rakesh Raut Jun 17 '16 at 13:19
1

ExpectedConditions.ElementExists will not be helpful in this case. Element has been found but is not clickable – qchar90 Dec 06 '19 at 13:04

score 0 · Answer 7 · answered Jun 21 '22 at 14:07

0

I had the similar issue with Chrome driver, changing the PageLoadStrategy of chromeOptions from 'Eager' to Normal fixed my problem.

chromeOptions.PageLoadStrategy = PageLoadStrategy.Normal;

answered Jun 21 '22 at 14:07

Rajat Maheshwari

1
1

Selenium-Debugging: Element is not clickable at point (X,Y)

7 Answers7

Linked

Related