Chrome - Element is not clickable at point

[lukeis]

Originally reported on Google Code with ID 2766

Selenium Webdriver for C#: 2.11.0
ChromeDriver.exe: 16.0.902.0
Chrome: 15.0.874.106 m

Is anyone else seeing this?

EXPECTED: Webdriver to click the link in Chrome

ACTUAL:
System.InvalidOperationException : Element is not clickable at point (326, 792.5)

Reported by jaemzware on 2011-11-03 13:47:28

[lukeis]

Reported by barancev on 2011-11-04 21:33:36

• Labels added: Component-WebDriver, Browser-Chrome

[lukeis]

Can you give a reproducible test case? Or a link to a public page where the problem
occurs?

Reported by kkania@chromium.org on 2011-11-08 17:37:00

[lukeis]

I can't give out credentials to the site, nor find an example online.  Essentially they're
span tags embedded in anchors (<a...><span...> ... </span></a>), and I'm trying to
click the span.  It works in FF and IE, and some cases in Chrome; however, I have not
been able to track down the distinction for the non-working case.

I've since worked around the issue by navigating directly to the href of the parent
anchor of the span.
driver.Navigate().GoToUrl(driver.FindElement(By.Id(embeddedSpanIdToClick)).FindElement(By.XPath("..")).GetAttribute("href"));

Thank you for the followup.

Reported by jaemzware on 2011-11-08 17:57:33

[lukeis]

Oh, and FYI this is running remote to a Virtual Machine.

Reported by jaemzware on 2011-11-08 18:13:41

[lukeis]

I can reliably trigger an 'Element is not clickable at point' exception with the attached
Python script.

$ python 2766_script.py 
Traceback (most recent call last):
  File "2766_script.py", line 13, in <module>
    main()
  File "2766_script.py", line 9, in main
    link.click()
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webelement.py",
line 45, in click
    self._execute(Command.CLICK_ELEMENT)
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webelement.py",
line 194, in _execute
    return self._parent.execute(command, params)
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webdriver.py",
line 153, in execute
    self.error_handler.check_response(response)
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/errorhandler.py",
line 126, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: u'Element is not clickable
at point (46, 622). Other element would receive the click: <li id="y1990s" class="ui-tabs-panel
ui-widget-content ui-corner-bottom">...</li> (WARNING: The server did not provide any
stacktrace information); duration or timeout: 203 milliseconds\nBuild info: version:
\'2.11.0\', revision: \'14431\', time: \'2011-10-28 16:27:42\'\nSystem info: os.name:
\'Windows XP\', os.arch: \'x86\', os.version: \'5.1\', java.version: \'1.7.0\'\nDriver
info: driver.version: RemoteWebDriver' ; Screenshot: available via screen ; Stacktrace:
Method newInstance0 threw an error in None 


Environment information:

Python library: 2.11.1
Chromedriver: 16.0.920.0
selenium-server-standalone-2.11.0.jar on Mac OS X 10.6.8 and Windows XP

Reported by sum1abi on 2011-11-10 15:52:48

---

- _Attachment: [2766_script.py](https://storage.googleapis.com/google-code-attachments/selenium/issue-2766/comment-5/2766_script.py)_

[lukeis]

Thanks for the reproducible case. ChromeDriver always clicks the middle of the element
in attempt to be faithful to what an actual user does. However, in your case, if you
open Chrome and navigate to http://www.freelancersunion.org/about/index.html, you'll
notice the link '1990s' is not clickable in the middle.

There are two ways to handle this currently:
1) Change/fix the page so that the user can click on the link in the middle.
2) Use the advanced user interactions API to click at the appropriate place in the
link. e.g.,
ActionChains(w).move_to_element_with_offset(link, 0, 20).click().perform()

I suppose most of the 'Element is not clickable at point' errors are due to the link
not actually being clickable in its middle. To check, open Chrome's developer tools
via Inspect Element and hover over the element that is being clicked. Check that the
middle of the bounding box that appears is actually clickable.

I'm going to mark this as WontFix. If you can find a reproducible case where the element
is actually clickable by the user at the middle, please reopen this bug.

Reported by kkania@google.com on 2011-11-15 21:48:08

• Status changed: WontFix

---

- _Attachment: click.png
_

[lukeis]

Here is my use case that produces the same "Element not clickable" error

1) I  have a page that have a link and a div in front of the link.
2) Without doing anything with the div, I can use xpath to find the link and it is
clickable.
3) Now if I hide that div, the same xpath still finds the link but the link becomes
not clickable.
4) Same code works for FF and IE.
5) My guess is that Chrome driver doesn't calculate the correct screen location of
link.

Reported by quyong2000 on 2011-12-05 17:43:07

[lukeis]

I'm having a legitimate error that I think is selenium's fault, not chrome's
I'm referencing an anchor inside a div. I know it is the webelement I'm interacting
with because I can get_attribute its href
I'm getting an error "Other element would receive the click, and it references the
parent div
This parent stretches across the page, so of course, chrome clicking in the middle
of it is not going to properly select the link.

Hardcoding coordinates is an absolutely horrible solution for writing non-brittle tests.
This needs to be investigated and fixed.

Reported by titus.fortner@tippr.com on 2011-12-06 16:39:08