Re: Issue 2766 in selenium: Chrome - Element is not clickable at point

[sele...@googlecode.com]

Comment #12 on issue 2766 by aditya.d...@gmail.com: Chrome - Element is not
clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

This problem has become a nightmare for me after upgrading chromedriver.exe
from 16.0.902.0 to 18.0.1022.0. Sometimes it works all fine and sometimes i
get this exception

org.openqa.selenium.WebDriverException: Element is not clickable at point
(849.5, 120.5).

Its kind of hard for me to maintain stability of the script as its
intermittent

[sele...@googlecode.com]

Comment #13 on issue 2766 by kka...@google.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

If you have a small test page that reproduces this problem (even if only
occasionally) that you can share, that would be helpful.

#12, I don't see any reason why it should fail intermittently, unless if
the element moves when ChromeDriver attempts to click it. This could
happen, e.g., if an ad pops up on the page and causes the link to be pushed
down all of a sudden. To test, you could try logging the location of the
element repeatedly and see if it ever changes. If the problem only occurs
very rarely, I'd catch the WebDriver exception thrown by the click, and in
the exception log the location of the element again. You can compare the
location where ChromeDriver attempted to click and the current location of
the element, which will let you know if the problem is because the element
moved. If that is the case, you need to wait for the page to be fully
loaded, or try clicking again, or we need to change the way clicking works
in ChromeDriver.

Also, see more details about the problem here:
http://code.google.com/p/chromedriver/wiki/TroubleshootingAndSupport

[sele...@googlecode.com]

Comment #14 on issue 2766 by aditya.d...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

yes you are right! The position of the element changes as the page starts
loading, so what i am doing is adding explicit wait before clicking the
element so that the page gets loaded, but believe me its really not
possible to add explicit waits before all such elements with which i face
this problem.
Note: I never ever faced this problem with chromedriver.exe 16.0.902.0 .

Is there any change in the way clicking works in ChromeDriver after
chromedriver.exe version 16.0.902.0 ?

I was totally relying on implicit waits till now , but after upgrading my
chromedriver.exe to 18.0.1022.0 , things are not like they were.

I don't have any public url on which i can reproduce the same issue. But i
think either its about implicit wait for page load or the way chrome driver
is clicking on the element.

And what i think is that its something related to implicit wait for page
load because i am getting these stale element exceptions quite frequently
after upgrade

org.openqa.selenium.StaleElementReferenceException: getElementTagName
execution failed;

They are intermittent too.

And again i had to add implicit waits.

[sele...@googlecode.com]

Comment #15 on issue 2766 by aditya.d...@gmail.com: Chrome - Element is not

org.openqa.selenium.StaleElementReferenceException: getElementTagName
execution failed;

They are intermittent too.

And again i had to add explicit waits.

[sele...@googlecode.com]

Comment #16 on issue 2766 by kka...@google.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

See the changes between the two versions here:
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=%2Ftrunk%2Fsrc%2Fchrome%2Ftest%2Fwebdriver&range=104253%3A119625&mode=html

I don't see any significant changes in clicking between the two. You may
want to star the following issue:
http://code.google.com/p/chromedriver/issues/detail?id=22

[sele...@googlecode.com]

Comment #17 on issue 2766 by aditya.d...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Is it possible that the time difference between finding an element and
performing action on it is bit large which might cause both the problems

1 Change is position of element
2 Reference to the element might go stale in that duration due to some
change in DOM.

Either this or its too fast that it tries to find element before the DOM is
in stable state and page is fully loaded , but when it performs action due
to change in DOM it throws the above mentioned exceptions.

But the above mentioned enhancement would be great. Hope it solves the
problem .

[sele...@googlecode.com]

Comment #18 on issue 2766 by mielu...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Hi,

I am having the same issue:

Element is not clickable at point (69.5, 677.5). Other element would
receive the click: <div id="background">...</div> (WARNING: The server did
not provide any stacktrace information) Command duration or timeout: 125
milliseconds Build info: version: '2.17.0', revision: '15540',
time: '2012-01-16 16:51:46' System info: os.name: 'Windows 7',
os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_30' Driver info:
driver.version: RemoteWebDriver Command duration or timeout: 904
milliseconds Build info: version: '2.17.0', revision: '15546',
time: '2012-01-16 17:11:34' System info: os.name: 'Linux',
os.arch: 'amd64', os.version: '2.6.32-5-amd64', java.version: '1.6.0_26'
Driver info: driver.version: RemoteWebDriver

This error is very inconsistent (it appears in 1 out of 5 runs). In FF and
IE works perfectly.
The issue appears after an image is loaded on the page and the element
position is moved.
Do you have a solution for this?

Thanks,
Bogdan

[sele...@googlecode.com]

Comment #19 on issue 2766 by kka...@chromium.org: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

The best way to currently avoid this problem is to wait for the element to
stop moving (wait for the page or image to finish loading in your case).

You may want to star

http://code.google.com/p/chromedriver/issues/detail?id=28 and/or
http://code.google.com/p/chromedriver/issues/detail?id=22 which would make
this issue go away.

Also, see
http://code.google.com/p/chromedriver/wiki/TroubleshootingAndSupport for
more info.

[sele...@googlecode.com]

Comment #20 on issue 2766 by mielu...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Hi,

Thanks for the fast reply. I've tried to wait for the page to load (the
issue appear after loading an image and also after removing the image -
this causes the element to 'move') and it didn't work. Only with
getLocation() method it seems stable, but this also fails sometimes (so far
it failed only once in about 50 runs - acceptable but not a solution)

Regards,
Bogdan

[sele...@googlecode.com]

Comment #21 on issue 2766 by kka...@google.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Besides waiting for the page to load, you should wait for the image to be
removed and any other event which is causing the element position's to
change. This sometimes can be difficult, which is why you might be
interested in the two feature requests logged on the chromedriver site I
mention above. If you can guarantee that the element is no longer moving,
clicking should work, even if it needs to scroll to do so.

[sele...@googlecode.com]

Comment #22 on issue 2766 by florentbr: Chrome - Element is not clickable
at point
http://code.google.com/p/selenium/issues/detail?id=2766

Here is a simple example with google search which works with IE and
Firefox, but fails with Chrome :

OpenQA.Selenium.Chrome.ChromeDriver driver = new
OpenQA.Selenium.Chrome.ChromeDriver();
driver.Navigate().GoToUrl(@"http://www.google.com");
driver.FindElementByName("q").SendKeys("Eiffel tower");
System.Threading.Thread.Sleep(1000);
driver.FindElementByName("btnG").Click();
KO : Element is not clickable at point (450, 268)

When the text to search is typed, a dropped down list is created and it
moves the search button.

[sele...@googlecode.com]

Comment #23 on issue 2766 by reddyma...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I upgraded chromedriver from
version=14.0.836.0
to
version=19.0.1068.0
and I keep getting the following error.
org.openqa.selenium.StaleElementReferenceException: getAttribute execution
failed;
The page I am loading has multiple Ajax calls. The Same code works with
Firefox which indicates something wrong with the new version of chrome
driver.
All test cases were working fine earlier for Chrome.

Any ideas how to fix this ?
Or should I roll back to older chromedriver version.

[sele...@googlecode.com]

Comment #24 on issue 2766 by alister....@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I am getting the same error using version 19

OpenQA.Selenium.StaleElementReferenceException: isDisplayed execution
failed;
Element does not exist in cache

[sele...@googlecode.com]

Comment #25 on issue 2766 by Mark.te...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Also getting the error: Element is not clickable at point...

ChromeDriver Version: 19.0.1068.0

Running through the test tutorial at
http://davidwinter.me/articles/2012/01/14/testing-javascript-websites-with-behat/
with one small change to the scenario: changed "When I press" to "When I
follow" as the "Launch demo modal" button on the
http://twitter.github.com/bootstrap/javascript.html page is an anchor.

@javascript
Scenario: Open modal dialog
Given I am on "/javascript.html"
And I should see "Launch demo modal"
When I follow "Launch demo modal"
Then I should see the modal "Modal Heading"
And I should see "Overflowing text to show optional scrollbar"

behat.yml

default:
context:
parameters:
base_url: http://twitter.github.com/bootstrap/
browser: chrome
javascript_session: webdriver

If I comment out browser the test uses Firefox. The test passes in Firefox
but fails in Chrome with this error:

When I follow "Launch demo modal" #
FeatureContext::clickLink()
Element is not clickable at point (378.5, 595.5). Other element would
receive the click: <div class="span9 columns">...</div> (WARNING: The

server did not provide any stacktrace information)

Command duration or timeout: 48 milliseconds
Build info: version: '2.21.0', revision: '16552', time: '2012-04-11
19:08:38'
System info: os.name: 'Mac OS X', os.arch: 'x86_64',
os.version: '10.7.4', java.version: '1.6.0_31'
Driver info: driver.version: RemoteWebDriver

Thanks

[sele...@googlecode.com]

Comment #26 on issue 2766 by manikand...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I am getting the same error message, with latest chrome v20.0, under same
circumstances...Element clickable in Firefox, but not so in Chrome
Webdriver...!

[sele...@googlecode.com]

Comment #27 on issue 2766 by m...@kabanasoft.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I ran into this same issue as well with Chrome...clicking the element works
fine in firefox but not in Chrome...the fix is pretty easy though, all you
have to do is scroll the element into view before clicking it, and you
won't run into this problem in Chrome. Here's the code i use:

IWebElement elementToClick = <code to get element>;

// Scroll the browser to the element's Y position
(driver as
IJavaScriptExecutor).ExecuteScript(string.Format("window.scrollTo(0,
{0});", elementToClick.Location.Y));

// Click the element
elementToClick.Click();

Hope this helps anyone else who runs into this issue

[sele...@googlecode.com]

Comment #28 on issue 2766 by richard....@ca.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I've run into this issue in several places while testing a bespoke ajax web
app and the scrollIntoView() workaround has always got me passed it.
However, I have a tree view driven by js in a popup off my main window and
I've found that I can only navigate down one-level in it, but not 2, before
hitting this error. I tried the usual workaround and also deliberately
getting the tree node's coords and clicking them explicitly; neither made
any difference - the 'Element is not clickable at point' error still
occurred.
The same script works fine in IE8/9 and ff12.
I'm using chromedriver 20.0.1133.0.

I can't send the example web page that fails as it is proprietary code and
distilling out the bit that fails is too much effort. :-(

[sele...@googlecode.com]

Comment #29 on issue 2766 by sergey...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Thanx for Comment 27 by m...@kabanasoft.com, Jun 13, 2012, it really helps,
but I've change some this script and now it works:

// 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();

[sele...@googlecode.com]

Comment #30 on issue 2766 by sergey...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Thanx for Comment 27 by m...@kabanasoft.com, Jun 13, 2012, it really helps,

I've change some this script for JAVA and now it works:

[sele...@googlecode.com]

Comment #31 on issue 2766 by deepak.s...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I am using python api binding and I am not able to find the advanced
interaction api that is mentioned here.
Can I get more information on how to prevent this bug. This is working in
Selenium RC.

[sele...@googlecode.com]

Comment #32 on issue 2766 by sergey...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

For python try this:

ActionChains(w).move_to_element_with_offset(link, 0, 20).click().perform()

[sele...@googlecode.com]

Comment #33 on issue 2766 by b...@bonamin.org: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

For ruby with Capybara the following line of code worked for me:

# Where @session is a Capybara::Session instance
# and object is a Capybara::Node::Element instance

@session.driver.execute_script "window.scrollTo(#{object.native.location.x},#{object.native.location.y})"
return_string = object.native.click

[sele...@googlecode.com]

Comment #34 on issue 2766 by b...@bonamin.org: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

For Ruby with Capybara and selenium-webdriver the following line of code

[sele...@googlecode.com]

Comment #35 on issue 2766 by amitjain...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

We am also getting similar issue, Even for me findElement throwing
exception.
Trying to test on Twitter.com and getting exception while entering UserName.

WebElement el = webDriver.getDriver().findElement(By.id("signin-email"));

Getting following exception

"org.openqa.selenium.WebDriverException: Element is not clickable at point
(943.5, 211.5). Other element would receive the click: <label
for="signin-email" class="placeholder">...</label> (WARNING: The server did

not provide any stacktrace information)

Command duration or timeout: 74 milliseconds
Build info: version: '2.26.0', revision: '18041', time: '2012-11-01
19:33:38'
System info: os.name: 'Windows NT (unknown)', os.arch: 'amd64',
os.version: '6.2', java.version: '1.6.0_34'
Driver info: driver.version: RemoteWebDriver

>>> Please let me know if any additional information is required.

[sele...@googlecode.com]

Comment #36 on issue 2766 by amitjain...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

We are also getting similar issue, Even for me findElement throwing
exception.

Trying to test on Twitter.com and getting exception while finding UserName.

[sele...@googlecode.com]

Comment #37 on issue 2766 by semple....@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

ActionChains(w).move_to_element_with_offset(link, 0, 20).click().perform()
worked for me. The link didn't need to be scrolled into view, but the click
needed to be repositioned. Previously I used sleep(1) and that worked 'most
of the time' (except when it didn't).

[sele...@googlecode.com]

Comment #38 on issue 2766 by arunbal...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I had the same issue of Chrome not able to click the Button when JavaScript
was updating the DOM to display the error message for failed coupon code. I
used the JavaScriptExecutor to fix my issue.

Code I used was:
JavascriptExecutor jsExecutor = (JavascriptExecutor) _driver;
jsExecutor.executeScript("
var InputElements = document.getElementsByTagName('input');"
+ "for (i=0; i<myelement.length; i++)"
+ "{"
+ "if(myelement[i].value == '<Text On Button>')"
+ "{"
+ "myelement[i].click();"
+ "}"
+ "}"
);

[sele...@googlecode.com]

Comment #39 on issue 2766 by arunbal...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I observed the issue of Chrome not able to click the Button when JavaScript

was updating the DOM to display the error message for failed coupon code.

On searching through Google, I observed this is common issue being faced
with Chrome and advanced User interactions like ActionBuilder or
JavaScriptExecutor can help solve the issue. I did not have success with
ActionBuilder but JavaScriptExecutor had the solution. Success of
JavascriptExecutor may be due to the fact, that JavaScript is well
supported by almost any web browser.

JavaScriptExecutor Code I used was:

// Create WebDriver instance of JavaScriptExecuor

JavascriptExecutor jsExecutor = (JavascriptExecutor) _driver;

//Execute the Javascript code of finding the input tag and searching
through the needed button among the input tags to click it with
executeScript function

jsExecutor.executeScript("

var InputElements = document.getElementsByTagName('input');"

+ "for (i=0; i<InputElements.length; i++)"

+ "{"

+ "if(InputElements[i].value == '<Text On Button>')"

+ "{"

+ "InputElements[i].click();"

+ "}"

+ "}"

);

[sele...@googlecode.com]

Comment #40 on issue 2766 by MPCro...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I was getting a lot of intermittent test failures with this issue. I was
able to stop them by giving the WebDriver process a low scheduling priority
using Linux's nice command.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[sele...@googlecode.com]

Comment #41 on issue 2766 by ronakpio...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I was also facing same issue.
System.InvalidOperationException : Element is not clickable at point (229,
82.5). Other element would receive the click:

Is there any way around for this?
Please let me know.

[sele...@googlecode.com]

Comment #42 on issue 2766 by er.vishv...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Same issuse observing--All test cases failed, Having lots of scenarios ,
Please have a look..

Element is not clickable at point (89, 19). Other element would receive the
click:

[sele...@googlecode.com]

Comment #43 on issue 2766 by ch.sreeh...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Even I am facing the same issue. I could reproduce with chrome driver 26.

Steps To Reproduce:
1) Open a page which has a tab.
2) Click on the tab. This time it is successful.

When you click on the same tab, it fails with the error. But with FF and
IE, it works fine.

Element is not clickable at point (253.5, 116.5). Other element would
receive the click: <div class="ext-el-mask" style="display: block;"></div>

(WARNING: The server did not provide any stacktrace information)

[sele...@googlecode.com]

Comment #44 on issue 2766 by sinkalat...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I had a similar problem a while ago.
Install an Xpath plugin in chrome if you haven't done so. I use XPath
helper which you launch by using ctr+shift+x. When I am using this plugin I
am able to see 'hidden' elements that might interfere with the one I am
interested in.

[sele...@googlecode.com]

Comment #45 on issue 2766 by Knure...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I've run into this bug. I found it because its only a problem with the
chrome driver, not the firefox driver (which I've been writing my tests in).

Working example to reproduce this issue (using webdriver):
1 - load page: http://s.codepen.io/anon/fullpage/gcmuf
2 - click element by css "input#b1" (works)
3 - click element by css "input#b2" (fails)

The wiki page briefly mentions this scenario "click an element fully or
partially under another element"
https://code.google.com/p/chromedriver/wiki/TroubleshootingAndSupport

Using webdriverjs, I have a work around using ActionSequence:
driver.actions().click(myElement).perform()
this is instead of
myElement.click()

I'm of the opinion that this is a work around to a bug, not something that
should be closed as WontFix.

[sele...@googlecode.com]

Comment #46 on issue 2766 by Knure...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

following up on my previous statement: this work-around doesn't actually
work

(It seems that my example isn't working as it was before, but the code can
be found here: http://codepen.io/anon/pen/gcmuf )
On that simple page there are 3 elements, with 2 of the elements hidden
behind a footer div. My first impression that it worked was because the 3rd
element allowed for the mouseMove to push the 2nd element into a viewable
space. In page I'm actually testing, there is no element below the link I
want to click.
The mouseMove only scrolls the page so that the link is within the window,
not far enough to go above the footer div.

[sele...@googlecode.com]

Comment #47 on issue 2766 by Automati...@spiraledge.com: Chrome - Element

is not clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Here is the link containing the element (e.g. remove) that we can click in
the middle.
http://www.yogaoutlet.com/shoppingcart.asp?itemaddedtocart=Y&relevant=2413&cartaddcode=45961

But when running with chrome driver, our automation cannot click on this
element (e.g. remove).

Notes: I used Xpath to get that element
public static IWebElement btn_remove(string productcode)
{
string btn_remove_xpath =
String.Format("//div[@class='shopped-item-name']//a[contains(@href,'{0}')]/../../..//a[contains(@href,'remove')]",
productcode);
try
{
return Yoga_Constant.wait.Until(d =>
d.FindElement(By.XPath(btn_remove_xpath)));
}
catch (Exception ae)
{
}
return null;

[sele...@googlecode.com]

Comment #48 on issue 2766 by barancev: Chrome - Element is not clickable at
point
http://code.google.com/p/selenium/issues/detail?id=2766

@Automat...@spiraledge.com: Please raise a new issue and provide an
executable sample that shows the issue (the provided link is personal).

[sele...@googlecode.com]

Comment #49 on issue 2766 by huguog...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I have the same error for Chrome driver only (IE driver works fine). Turns
out the fix for my specific case is easy, just sleep a few seconds before I
call the click method. Seems there is a gap between element is available
and time it is clickable (for Chrome driver only).

Sample C# code below (web page is ExtJS 4.2):
//Works in IE without the sleep
//IWebDriver driver = new
InternetExplorerDriver(@"d:\selenium");
IWebDriver driver = new ChromeDriver(@"d:\selenium");
driver.Navigate().GoToUrl("http://...");

WebDriverWait wait = new WebDriverWait(driver,
TimeSpan.FromSeconds(10));
IWebElement btn = wait.Until<IWebElement>((d) =>
{
return d.FindElement(By.Id("button-xxxx-btnInnerEl"));
});
Thread.Sleep(5000); //it works after added this sleep statement
btn.Click();

[sele...@googlecode.com]

Comment #50 on issue 2766 by sergey...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

So, click to element is really to use for example with using JavaScript and
coordinates of clicking point, but what must I do if I need to attach file
in chrome using type?

Attachments:
type.png 87.3 KB

[sele...@googlecode.com]

Comment #51 on issue 2766 by armyofda...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I was getting the same 'Element is not clickable at point' error. For me,
my input radio elements are hidden (replaced with 'nice' images for on/off
states)... FF didn't have an issue checking the hidden input by doing
something like:

driver.findElement(By.id("question1_b")).click();
but Chrome and IE never could find those elements to click... but i could
figure out the parent label via xpath, and clicking that worked in all
browsers:
driver.findElement(By.xpath("//label[.//input/@id='question1_b']")).click()

[sele...@googlecode.com]

Comment #52 on issue 2766 by vsingh.r...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

This is also possible due to other ajax component are not loaded. Selenium
pickup the element but not able to click. put some explicit wait and then
click the element , It will work.

[sele...@googlecode.com]

Comment #53 on issue 2766 by mmakelai...@alpha-sense.com: Chrome - Element

is not clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I'm seeing this too. Works on FF, not on Chrome.

I'm trying to click a tickbox, scroll into view with:

((Locatable) element).getCoordinates().inViewPort();
element.click();

Works in that Chrome will scroll the entry into view, but only to the point
where the bottom of the tickbox is not visible. FF will click the box
anyway, Chrome complains that it can't click the object. I've attached a
screenshot.

I'm actually in a menu so the standard javascript hack of scrolling doen't
work.

Attachments:
tickbox_notvisible.png 7.5 KB

[sele...@googlecode.com]

Comment #54 on issue 2766 by ani01...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I am also facing the same problem...
here is the code..
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;


public class SpecificLinks_Secondway {

public static void main(String[] args) throws InterruptedException {

System.setProperty("webdriver.chrome.driver", "D:\\SeleniumT\\chromedriver.exe");
ChromeDriver driver = new ChromeDriver();


//WebDriver driver = new FirefoxDriver();

driver.get("http://bbc.com");


String part1 = "//*[@id='news_moreTopStories']/ul/li[";
String part2 = "]/a";
for(int i=1;i<=5;i++){
WebDriverWait wait = new WebDriverWait(driver, 6);
Thread.sleep(10000);

wait.until(ExpectedConditions.elementToBeClickable(By.xpath(part1+i+part2)));
String text = driver.findElement(By.xpath(part1+i+part2)).getText();
System.out.println(text);
Thread.sleep(10000);
if (driver.findElement(By.xpath(part1+i+part2)).isDisplayed())
driver.findElement(By.xpath(part1+i+part2)).click();
System.out.println(driver.getTitle());
//driver.navigate().back();
driver.navigate().back();
//Thread.sleep(5000);
}

}

}


The output of the program:
Starting ChromeDriver (v2.8.241075) on port 9162
Stuck Antarctic ship close to rescue
Exception in thread "main" org.openqa.selenium.WebDriverException: unknown
error: Element is not clickable at point (503, 468). Other element would
receive the click: <li>...</li>
(Session info: chrome=31.0.1650.63)
(Driver info: chromedriver=2.8.241075,platform=Windows NT 6.1 SP1 x86_64)

(WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 49 milliseconds
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16
16:11:15'
System info: host: 'ANICHATT-LAP1', ip: '192.168.0.100', os.name: 'Windows
7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_45'
Session ID: de8bbcd4f76aea4f6e4d3d85b3a82b23
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true,
browserName=chrome,
chrome={userDataDir=C:\Users\ANICHA~1.ORA\AppData\Local\Temp\scoped_dir5356_6673},
rotatable=false, locationContextEnabled=true, version=31.0.1650.63,
takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false,
handlesAlerts=true, browserConnectionEnabled=false, nativeEvents=true,
webStorageEnabled=true, applicationCacheEnabled=false,
takesScreenshot=true}]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
at
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:554)
at
org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
at
org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
at SpecificLinks_Secondway.main(SpecificLinks_Secondway.java:52)

[sele...@googlecode.com]

Comment #55 on issue 2766 by ani01...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

btw the above code works perfectly in Firefox..

[sele...@googlecode.com]

Comment #56 on issue 2766 by alex.gro...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

i found a work around. for me, I have 2 tests.

1 chrome tablet works perfect.

2nd desktop fails at my loop which clicks on "cards" that it int's, however
if I maximize, my function will fail with the error message that is
dominant in this thread.

if you resize your window right before you click or avoid maximizing, then
you should be fine. its unreal that this is happening.

[sele...@googlecode.com]

Comment #57 on issue 2766 by hiteshpa...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Thanks, below code is working in my case.

Capabilities cp = ((RemoteWebDriver)
driver).getCapabilities();
if (cp.getBrowserName().equals("chrome")) {
try {
((JavascriptExecutor) driver).executeScript(
"arguments[0].scrollIntoView(true);",
webElement);
} catch (Exception e) {

}
}

webElement.click();

[sele...@googlecode.com]

Comment #58 on issue 2766 by rafaelc...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

what is the solution?

[sele...@googlecode.com]

Comment #59 on issue 2766 by mayanksa...@tk20.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

using javascriptexecutor resolves the issue...
is there any drawback of using javascriptexecutoy

[sele...@googlecode.com]

Comment #60 on issue 2766 by mayank3...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

using javascriptexecutor resolved the issue..
is there any drawback of using the javascriptexecutor

[sele...@googlecode.com]

Comment #61 on issue 2766 by aaronbr...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Updating chromedriver to version 2.9 resolved this issue for me
(http://chromedriver.storage.googleapis.com/index.html).

[sele...@googlecode.com]

Comment #62 on issue 2766 by st...@swipetospin.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Comment #27 is right on. If you need to do the same workaround in Python,
code similar to this should do it:

def scroll_to_and_click(xpath):
element = TestUtil.driver.find_element_by_xpath(xpath)
TestUtil.driver.execute_script('window.scrollTo(0, ' +
str(element.location['y']) + ');')
element.click()

[sele...@googlecode.com]

Comment #64 on issue 2766 by hellosha...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

My code is failing at: findElement(Using.EDIT_LINK.selector).click();
Error message:
org.openqa.selenium.WebDriverException: unknown error: Element is not
clickable at point (990, 4). Other element would receive the click: <div
id="ghDividerCart" class="dividerCartActive"></div>
(Session info: chrome=35.0.1916.114)
(Driver info: chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_64)

(WARNING: The server did not provide any stacktrace information)

Actually, EDIT link is visible on the page. The same code is working
perfectly in Firefox. Please help, what is wrong here.

[sele...@googlecode.com]

Comment #65 on issue 2766 by barancev: Chrome - Element is not clickable at
point
http://code.google.com/p/selenium/issues/detail?id=2766

Watch issue https://code.google.com/p/chromedriver/issues/detail?id=28

[sele...@googlecode.com]

Comment #66 on issue 2766 by natalia....@mulesoft.com: Chrome - Element is

not clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Thanks for comment #30. It totally solved the issue that has been racking
my brain for the past 4 days!!!

[sele...@googlecode.com]

Comment #67 on issue 2766 by tcjcolor...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Just to chime in on this issue. I am seeing this in C# and here is the
scenario.

I have a standard application form and when I clear an input field (ex.
FirstName, we have validation that drops below the field name to state the
field is required. Since this drops down a few pixels to add the validation
text, all fields in that section also drop down and then chrome starts
throwing the errors:

System.InvalidOperationException: unknown error: Element is not clickable
at point (968, 360). Other element would receive the click: <th>...</th>
(Session info: chrome=35.0.1916.153)
(Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64)

No issues with Firefox or IE.

[sele...@googlecode.com]

Comment #68 on issue 2766 by andriy.v...@indigitus.ch: Chrome - Element is

not clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Workarround.

Reproducible on: chromedriver=2.10.267518,platform=Linux 3.11.0-24-generic
x86_64
Not reproducible: Firefox

Error traceback:
Selenium::WebDriver::Error::UnknownError: unknown error: Element is not
clickable at point (248, 296). Other element would receive the click: <div
class="modal-backdrop in"></div>
(Session info: chrome=35.0.1916.153)
(Driver info: chromedriver=2.10.267518,platform=Linux 3.11.0-24-generic
x86_64)

Cause:
In my case issue caused by temporary element (you can see it form error
text) that appears after modal window is submitted.

Workarround:
In my case div (or other element from traceback) is temporary so you can
use method that waits until this element disappears. For example in
Watir/Ruby it is - wait_while_present. Example:

@browser.div(:class => 'modal-backdrop in').wait_while_present
@browser.link(:text => 'link_text').click

[sele...@googlecode.com]

Comment #69 on issue 2766 by avoroble...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Workarround.

Reproducible on: chromedriver=2.10.267518,platform=Linux 3.11.0-24-generic
x86_64
Not reproducible: Firefox

Error traceback:
Selenium::WebDriver::Error::UnknownError: unknown error: Element is not
clickable at point (248, 296). Other element would receive the click: <div
class="modal-backdrop in"></div>
(Session info: chrome=35.0.1916.153)
(Driver info: chromedriver=2.10.267518,platform=Linux 3.11.0-24-generic
x86_64)

Cause:
In my case issue caused by temporary element (you can see it form error
text) that appears after modal window is submitted.

Workarround:
In my case div (or other element from traceback) is temporary so you can

use method that waits untill element disappears. For example in Watir/Ruby

[sele...@googlecode.com]

Comment #70 on issue 2766 by arran.hu...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

That isn't a workaround. That is precisely what you should be doing in the
first place.

Selenium or ChromeDriver cannot possibly know your application has a modal
dialog that fades in & out. It's your tests responsbility to *not* carry on
with it's tasks *until* that dialog is there/not there.

[sele...@googlecode.com]

Comment #71 on issue 2766 by avoroble...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

to #70 arran.hu...@gmail.com
Firefox driver don't think so.

[sele...@googlecode.com]

Comment #72 on issue 2766 by avoroble...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

to #70 arran.hu...@gmail.com

1. Firefox driver don't think so.
2. After modal window is submitted div element that fades temporary should
not influence click on link since link is visible at the moment of click
and I use only text to locate link (so div element don't influence link
locator).

[sele...@googlecode.com]

Comment #73 on issue 2766 by avoroble...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

to #70 arran.hu...@gmail.com
1. Firefox driver don't think so.
2. After modal window is submitted div element that fades temporary should
not influence click on link since link is visible at the moment of click

and I use only text to locate link (so div element don't influence on link

[sele...@googlecode.com]

Comment #74 on issue 2766 by arran.hu...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

You'll need to provide more information, but I stand by my comment. That's
all the message means, that's the element you *want* to click is *not*
available *to be clicked*.

If you have a modal dialog, it's usually that the dialog is *in front of*
that element.

You will then have to wait for the dialog to disappear (fully) before doing
anything.

[sele...@googlecode.com]

Comment #75 on issue 2766 by rki...@crri.co.in: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Problem with chrome is if one element overlaps with other element it is not
able to recognize which element to click so this problem occurs

[sele...@googlecode.com]

Comment #76 on issue 2766 by rkhebba...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Problem with chrome is if one element overlaps with other element it is not

able to recognize which element to click.when this problem occurs it will
show "Element is not clickable at point Other element would receive the
click"

[sele...@googlecode.com]

Comment #77 on issue 2766 by n...@wsidevteam.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

nikhil...@gmail.com
i am facing it in firefox also.

the execution stopped itself without giving any error, where a clickable
event needs to be performed. what could be the possible solutions..??

[sele...@googlecode.com]

Comment #78 on issue 2766 by n...@wsidevteam.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

[sele...@googlecode.com]

Comment #79 on issue 2766 by barancev: Chrome - Element is not clickable at
point
http://code.google.com/p/selenium/issues/detail?id=2766

Watch the issue https://code.google.com/p/chromedriver/issues/detail?id=28

[sele...@googlecode.com]

Comment #80 on issue 2766 by yi1z...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I'm also getting this problem on the latest version of Chrome. I tried a
few solutions like scrolling to the button before clicking and scrolling
the screen so the button isn't hidden but these solutions aren't reliable.

Anything else I can try?

[sele...@googlecode.com]

Comment #81 on issue 2766 by chris.mo...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

Let's not forget this problem occurs when the element can certainly be
clicked by a user. The problem is that the click point is tested for
clickability but this is hard-coded to be the geometric center of the
target element. Imagine an element that is three times larger than the
viewport. When scrolled to top, its centre will be below the fold and
therefore not "clickable". The element can be clicked by the user on any
part of its hit area (alpha mask).

Another example is if only the geometric centre pixel is covered by another
element, then the entire element is deemed (incorrectly) to be unclickable
by a user.

[sele...@googlecode.com]

Comment #82 on issue 2766 by klas.flo...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

For me this was the reason of this happening:

It seems that if the web browser have other tasks to do like executing
scripts, Selenium/Chrome driver is faster to decide where the element
should appear and tries to click that position before it appears in the
browser. Then another element would recieve the click.

My workaround:
Wait between findElement and clicking.

WebDriverWait waitDriver = new WebDriverWait(driver, seconds);
waitDriver.until(ExpectedConditions.presenceOfElementLocated(By.xpath(xPath)));
WebElement element = driver.findElement(By.xpath(xPath));
Thread.sleep(3000);//Time to wait for me
element.click();

This is certainly a chromedriver bug if you ask me... would be great if it
could be fixed.

[sele...@googlecode.com]

Comment #83 on issue 2766 by DAvdo...@gmail.com: Chrome - Element is not

clickable at point
http://code.google.com/p/selenium/issues/detail?id=2766

I had the same issue:

unknown error: Element is not clickable at point (109, 775). Other element
would receive the click: <div class="mask" style="height: 3659px;"></div>
(Session info: chrome=32.0.1700.107)
(Driver info: chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86)

For me the Solution was:

var SaveAndClose = GetElementWaitVisibleThrow(By.Id("media_show"));
Actions action = new Actions(driver);
action.MoveByOffset(SaveAndClose.Location.X + 5, SaveAndClose.Location.Y +
5).Click().Perform();

[sele...@googlecode.com]

Comment #84 on issue 2766 by cbaqu...@temperies.com: Chrome - Element is
not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

I was having the same problem on a modal window, apparently with no reason,
because the button was visible and could interact with it. I was looking
for the element by name and having the same problem. Then changed to id or
css selector and it worked.
Also, a workaround for my case (particularly the button WAS visible) could
be changing the z-index in the UI implementation, so the button having a
greater z-index than the pop-up div would bring it to the front and the
location would now work.

Cheers,
Carolina.-

[sele...@googlecode.com]

Comment #85 on issue 2766 by corinne....@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

I had this problem too:

WebDriverException: Message: u'unknown error: Element is not clickable at
point (686, 713). Other element would receive the click: <div
id="cab-wrapper" style="width: 700px; display: block;">...</div>\n
(Session info: chrome=37.0.2062.122)\n (Driver info:
chromedriver=2.10.267517,platform=Mac OS X 10.9.3 x86_64)'

The same tests pass using Safari, Firefox, and IE drivers.

Tried most of the fixes described here: (i) scrolling to the element on the
page, (ii) changing the z-index of the element, (iii) off-setting the click
by a few pixels, (iv) changing the locator to using an id or css selector.
None of these fixes worked for me: what finally *did* work was just finding
the element by whatever means I wanted (xpath/class/css/id/etc) and then
executing the Javascript click command:

self.browser.execute_script("arguments[0].click();", btn)

Hope this helps!

[sele...@googlecode.com]

Comment #86 on issue 2766 by brent.at...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

I am experiencing this as well. Using execute_script worked for me as
corinne described.

I can't speak for everyone's case, but the issue I'm experiencing is my
webdriver code is executing before page is completely set up. If I run the
test cases manually on a loaded page, everything works fine. If I run the
test suite full speed, which loads the page and immediately clicks, I get
this error. I suspect that using the script works because it defers
clicking the element long enough for the document to be ready.

In my case, the page uses the jQuery BlockUI plugin
(http://malsup.com/jquery/block/) to simulate a modal by positioning a div
over the entire page. When this error occurs, the element webdriver
complains about is the div added by the BlockUI plugin.

[sele...@googlecode.com]

Comment #87 on issue 2766 by schuette...@googlemail.com: Chrome - Element

is not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

I can confirm this bug and the workaround to use JavaScript. It's a very
annoying thing... :(

[sele...@googlecode.com]

Comment #88 on issue 2766 by muham...@baublebar.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Have tried all the means, jsexecuter, actions class, nothing helped.
Finally Thread.sleep worked but as you all know it is not preferred.
Surely this should be a bug.

Any solutions will be greatly appreciated.

[sele...@googlecode.com]

Comment #89 on issue 2766 by nor.dhin...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Its really annoying ...Pls help me out of this ,...

[sele...@googlecode.com]

Comment #90 on issue 2766 by paulmurp...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Make sure the element is in view, then click it using native actions,
worked for me, but one of them on thier own did not work.

[sele...@googlecode.com]

Comment #91 on issue 2766 by vchernoi...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Run into the same issue. Please look at the picture attached
It feels like a wrong assumption is made which element is on the top based
on z-index.

There is a gray "background" which has z-index=999 and a pseudo-modal
overlay dialog which has z-index=1000.
All elements inside the latter are on the top of the first, but since they
have no
their own z-index it is assumed to be under the background.

Unfortunately I have no access to the site code to make corrections in
order check the guess. Will update this later

Attachments:
Selection_010.png 256 KB

[sele...@googlecode.com]

Comment #92 on issue 2766 by kavishae...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Hi!
In my js page, I had this code:
$('body').css('cursor', 'wait');
before the processing in this page starts.
and then this:
$('body').css('cursor', 'default');
after the processing is complete.

Like a lot of people told in the forum, to wait till this page load
completes.
So i tried this,
(new WebDriverWait(driver, 10))
.until(new ExpectedCondition<Boolean>() {
public Boolean apply(WebDriver d) {
WebElement elm = driver.findElement(By.tagName("body"));
String cssValue = elm.getCssValue("cursor");
boolean cssWait = false;

if(cssValue.equals("default")){
cssWait = true;
}
return cssWait == true;
}
});
And it worked!
I am just two days old to Selenium, so excuse me in this solution is not a
great one.
But it worked, so posting it here.

[sele...@googlecode.com]

Comment #93 on issue 2766 by ankitrat...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Thanks corinne....@gmail.com

This worked for me

[sele...@googlecode.com]

Comment #94 on issue 2766 by romelber...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

#94 bernas...@yahoo.com

chrome uses point location.
browser appears to be minimize (1024X768) when you are using larger screens
with large resolutions like mine (1366X768) making chrome driver to point
on wrong location.

fix: (im using java)

driver.manage().window().maximize();

it worked for me

[sele...@googlecode.com]

Comment #95 on issue 2766 by pardhiv...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

0 down vote


I downloaded the latest chrome driver from www.seleniumhq.org and and also
latest selenium jar file 2.44 version and ran using this code and I could
make the element be clickable.

Code used is

// Find an element and define it WebElement elementToClick =
D9.findElement(By.xpath("xpathcode"));

// Scroll the browser to the element's Y position

((JavascriptExecutor)
D9).executeScript("window.scrollTo(0,"+elementToClick.getLocation().y+")");

// Click the element

elementToClick.click();

Thanks,

Pardhiva E.

[sele...@googlecode.com]

Comment #96 on issue 2766 by GlassM...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

After some significant frustration, I have solved this issue for my
problem. I got this error in Chrome, but not Firefox. What tipped me off
what my screenshots did not quite scroll to the bottom, even though I ran:
((IJavaScriptExecutor) driver).ExecuteScript("window.scrollTo(0,
document.body.scrollHeight);");

I clicked on an element that populated a table. The table was still
populating, when the screenshot occurred, and consequently, the position of
the button would also change slightly. Meaning, the table was growing when
I was about to click on the element.

[sele...@googlecode.com]

Comment #97 on issue 2766 by homebrew...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Here's my solution:

void clickByAction(By locator){
waitUntilElementIsPresent(locator)
WebElement element = driver.findElement(locator)
Actions actions = new Actions(driver)
actions.moveToElement(element).click().perform()

[sele...@googlecode.com]

Comment #98 on issue 2766 by el...@perrysysinc.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

@romel

This worked for me also, thanks for the fix!

driver.manage().window().maximize();

[sele...@googlecode.com]

Comment #99 on issue 2766 by nordicwa...@googlemail.com: Chrome - Element

is not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

This issue is still very annoying.
I have lots of test that work perfectly with FirefoxDriver but won't work
with ChromeDriver.

unknown error: Element is not clickable at point (723, 616). Other element
would receive the click: <div class="blockUI blockOverlay" style="z-index:
1000; border: none; margin: 0px; padding: 0px; width: 100%; height: 100%;
top: 0px; left: 0px; opacity: 0.2; cursor: wait; position: fixed;
background-color: rgb(192, 192, 192);"></div>

Example of my code:

WAIT.until(ExpectedConditions.visibilityOfElementLocated(By.xpath(changeSizeColorXPath.get())));
changeSizeColor = findElementByXPath(changeSizeColorXPath);
changeSizeColor.click();


I tried the maximize workaround. Still not working..

[sele...@googlecode.com]

Comment #100 on issue 2766 by jerry.ma...@sitebot.org: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Issue was fixed for my case when I increased the sleep timer.

Thread.sleep(60000);

[sele...@googlecode.com]

Comment #101 on issue 2766 by Hubert.T...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

This is quite good workaround made by me:
I have made my method that uses selenium click method.
first I made a loop that tries to click 'n' times in a row if prevoius try
failed.
public static void myClick(WebElement element)
e.g. n=5

int n=5;
for (int i=1; i<=n; i++)
{
try {
element.click();
break;
} catch(WebDriverException driverException) {
System.out.println("Click on element failed. Attempt: "+i+"/"+n)
Thread.sleep(1000);
}
if(i==n)
{
Assert.fail("Failed to click "+n+" times");
}
}

It will work 99% of time, cose sometimes element is not yet click able,
sometimes browser could not scroll fast enough to element (so second check
will work), sometimes animation of element or server response is too long,
and most times because of so called 'f**k you' error.

[sele...@googlecode.com]

Comment #102 on issue 2766 by n...@webon.net: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

I have no idea why some element are not clickable via Chrome driver.
But when I use java script to force click the element, it's work properly.

Maybe the Chrome web driver handle elements different from another driver.

WebElement we = driver.findElement(By.cssSelector("#productListing *
td.product-name-td > a:nth-child(1)"));
WrappedPack.clickHiddenElement(driver, we);

[sele...@googlecode.com]

Comment #103 on issue 2766 by Hubert.T...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

If you do not use waits, it's possible for ChromeDriver to click element
before it is even loaded properly... You should use waits to check if
element is clickable and then run click.

[sele...@googlecode.com]

Comment #104 on issue 2766 by jpsow...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

If you are using BrowserLink in Visual Studio 2013, Browserlink will
display a navbar at the bottom of the browser page. If the item you want to
click is behind that navbar, you will get an error that the wrong thing
will be clicked. Disabling BrowserLink fixed this issue for me.

[sele...@googlecode.com]

Comment #105 on issue 2766 by serhiiak...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

OMG! It is still not fixed. Fair enough! 2 years passed

[sele...@googlecode.com]

Comment #106 on issue 2766 by mike.scr...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Come on Google, this is definitely not 'Won't fix' material. Sometimes I
can't believe I'm writing special code for Chrome while IE is passing with
flying colors.

[sele...@googlecode.com]

Comment #107 on issue 2766 by manisund...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

This issue may happen which element we gonna click that might not be in
browser visible area. I have this issue on below scenarios

My browser scroll bar automatically went middle of page due to more number
table row in the current page which i wants to navigate and perform. But my
expected clickable element present at the top of the page. So here chrome
driver searching the element from current visible area from to bottom.(not
searching/finding the top element).

Due to this reason I have faced this at clickable at (x,y) issue in chrome
browser. Finally I fixed this using "((JavascriptExecutor)
driver).executeScript("window.scrollTo(0,0)");" before my expected element
click.

[sele...@googlecode.com]

Comment #108 on issue 2766 by manisund...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

This issue may happen which element we gonna click that might not be in

browser visible area. I have faced this same issue on below scenarios

My browser scroll bar automatically went middle of page due to more number
table row in the current page which i wants to navigate and perform. But my
expected clickable element present at the top of the page. So here chrome
driver searching the element from current visible area from to bottom.(not
searching/finding the top element).

Due to this reason I have faced this at clickable at (x,y) issue in chrome
browser. Finally I fixed this using "((JavascriptExecutor)
driver).executeScript("window.scrollTo(0,0)");" before my expected element
click.

Now driver visible area went to top, from there it start search from top to
bottom.

[sele...@googlecode.com]

Comment #109 on issue 2766 by jaemzw...@gmail.com: Chrome - Element is not

clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Take screenshot right before and after (i.e. in a catch block) the error
occurs, if you haven't already. If you need help with this, I can paste
sample code.

[sele...@googlecode.com]

Comment #110 on issue 2766 by yunhanch...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Have the same the issue here
Exception: unknown error: Element is not clickable at point (432, 785).
Other element would receive the click: <div class="modal-backdrop fade in"
ng-class="{in: animate}" ng-style="{'z-index': 1040 + index*10}"
ng-click="close($event)" modal-backdrop="" style="z-index: 1040;"></div>

Driver info: chromedriver=2.15.322455
(ae8db840dac8d0c453355d3d922c91adfb61df8f),platform=Mac OS X 10.9.5 x86_64

Find a workaround is just a hacky way to click space outside modal to
dismiss that. But ideally we want the button to be clickable
Anyone have other solution?

[sele...@googlecode.com]

Comment #111 on issue 2766 by aditya.d...@gmail.com: Chrome - Element is

not clickable at point
https://code.google.com/p/selenium/issues/detail?id=2766

Try using webdriver wait with expected conditions

Ex:
WebDriverWait wait = new WebDriverWait(driver, 15);
wait.until(ExpectedConditions.elementToBeClickable(By.cssSelector("#submitButton")));

If you wanna read more
http://seleniumeasy.com/selenium-tutorials/webdriver-wait-examples.

[sele...@googlecode.com]

Comment #112 on issue 2766 by logichype: Chrome - Element is not clickable
at point
https://code.google.com/p/selenium/issues/detail?id=2766

I found this issue while writing webdriver scripts for a mobile application
written with jquery mobile. Everything runs fine in firefox, but when I
changed to chrome suddenly it just blows up on like the 3rd step, never
mind the other hundreds of steps that firefox will run through. The
element which fails (a checkbox) has been "enhanced" for mobile viewing via
the jqm library, and I suppose maybe the underlying "checkbox" is not
visible. However, semantically and practically it is still there and
should work the same. That's the idea of progressive enhancement, the raw
semantics don't change just the presentation. This is a very common
library and it appears that this type of mobile app is untestable with
chrome webdriver. One thought is that you could use a "strict" option to
the driver config which might disable this "extra checking". Certainly it
is intended to be helpful but it does not end up helping in every real
world case. I really hate to add any hackish workarounds to fix this. The
semantics are clear and the test script should be based on simple ideas
like "click the checkbox" not "find the div that has xyz class that is
surrounding the checkbox and click it (and pray these things don't
change)". If other browser drivers are doing it without issues, why not
chrome? I guess I'll go hack some javascript or something ugly, since I
can't hold my breath until 2019 to see if someone cares enough to look at
this again. But don't let that stop you, it is too late for me, but other
people will need the fix, help them.