Debugging Element is not clickable at point error

Question

I see this only in Chrome   The full error message reads       org openqa selenium WebDriverException  Element is not clickable at point  411  675   Other element would receive the click         The element that  would receive the click  is to the side of the element in question  not on top of it and not overlapping it  not moving around the page   I have tried adding an offset  but that does not work either   The item is on the displayed window without any need for scrolling

User · Answer

WebDriverWait wait   new WebDriverWait driver  TimeSpan FromSeconds 15    wait Until SeleniumExtras WaitHelpers ExpectedConditions ElementToBeClickable By  lt Id or anything gt       Hope this helps

User · Answer

You may simulate click with JS   public void click WebElement element        JavascriptExecutor js   JavascriptExecutor driver      js executeScript  document elementFromPoint     element getLocation   x         element getLocation   y      click

User · Answer

I had the same issue and got the  other element would receive the click  error for a displayed  visible element  I found no other solution that to trigger the click with a javascript   I replaced   WebElement el   webDriver findElement By id  undo-alert     WebElement closeButton   el findElement By className  close        The following throws  Element is not clickable at point     Other element     would receive the click  closeButton click      with     JavascriptExecutor  webDriver  executeScript           undo-alert   find   close   click          and it all worked out fine

User · Answer

The reason for this error is that the element that you are trying to click is not in the viewport  region seen by the user  of the browser  So the way to overcome this is by scrolling to the desired element first and then performing the click   Javascript   async scrollTo  webElement        await this driver executeScript  arguments 0  scrollIntoView true    webElement      await this driver executeScript  window scrollBy 0 -150        Java   public void scrollTo  WebElement e        JavascriptExecutor js    JavascriptExecutor  driver       js executeAsyncScript  arguments 0  scrollIntoView true    e      js executeAsyncScript  window scrollBy 0 -150

User · Answer

There seems to be a bug in chromedriver for that  the problem is that it s marked as won t fix  --  GitHub Link   place a bounty on FreedomSponsors perhaps    There s a workaround suggested at comment  27  Maybe it ll work for you-

User · Answer

Try to maximize the browser when you are working with resolutions greater than 1024x768   driver manage   window   maximize

User · Answer

In my case  it worked in Firefox but failed in Chrome  In Chrome  it got fixed after updating Chrome driver version to the latest

User · Answer

Wow  a lot of answers here  and many good ones   I hope I ll add something to this from my experience   Well guys  in my case there was a cookie overlay hiding the element occasionally  Scrolling to the element also works  but in my humble opinion  for my case  not a panacea for everyone  the simplest solution is just to go full screen  I was running my scripts on a 3 4 of the screen window   So here we go   driver manage   window   maximize      Hope that helps

User · Answer

You need to use focus or scroll on that element  You also might have to use explict wait   WebElement firstbutton  driver findElement By xpath  Your Element     Actions actions   new Actions driver   actions moveToElement element   actions perform      OR  The element is not clickable because of a Spinner Overlay on top of it   By loadingImage   By id  loading image ID    WebDriverWait wait   new WebDriverWait driver  timeOutInSeconds   wait until ExpectedConditions invisibilityOfElementLocated loadingImage      OR  Point p  element getLocation    Actions actions   new Actions driver   actions moveToElement element  movebyoffset p x p y  click   perform      OR  If still not work use JavascriptExecutor   JavascriptExecutor executor    JavascriptExecutor driver  executor executeScript  arguments 0  click      firstbutton

User · Answer

Instead of  webdriver findElement By id  id1    click      try to use  click By id  id1      void click final By byLocator        waitFor new ExpectedCondition lt Boolean gt               Override         public Boolean apply WebDriver driver                WebElement element   driver findElement byLocator               if  element isDisplayed                      try                       element click                        return true                    catch  Exception e                        e printStackTrace                                                return false                      Override         public String toString                 return  Element located     byLocator     clicked

User · Answer

After testing all mentioned suggestions  nothing worked  I made this code  It works  but is not beautiful  public void click WebElement element          https   code google com p selenium issues detail id 2766  fix      while true           try              element click                break           catch  Throwable e               try                   Thread sleep 200                 catch  InterruptedException e1                    e1 printStackTrace                                     public void click String css          https   code google com p selenium issues detail id 2766  fix      while true           try              driver findElement By cssSelector css   click                break           catch  Throwable e               try                   Thread sleep 200                 catch  InterruptedException e1                    e1 printStackTrace

User · Answer

I was getting this bug because I tested a hover and then needed to click on the link underneath the tooltip  The solution was to add page find   sp-logo   hover before click link to get the tooltip out of the way

User · Answer

If you re using the line below in your conf js file  please comment it out and try again  browser ignoreSynchronization   true

User · Answer

This might happen if the element changes position while the driver is attempting to click it  I ve seen this with IE too   The driver retains the initial position but by the time it actually gets to clicking on it  that position is no longer pointing to that element  The FireFox driver doesn t have this problem BTW  apparently it  clicks  elements programmatically   Anyway  this can happen when you use animations or simply change the height of elements dynamically  e g      foo   height 500    You need to make sure that you only click elements after their height has  settled   I ended up with code that looks like this  C  bindings    if    driver is FirefoxDriver         new WebDriverWait driver  TimeSpan FromSeconds 10   Until          d   gt  d FindElement By Id someDynamicDiv   Size Height  gt  initialSize       In case of an animation or any other factor you can t easily query for  you can utilize a  generic  method that waits for the element to be stationary   var prevLocation   new Point Int32 MinValue  Int32 MinValue   int stationaryCount   0  int desiredStationarySamples   6    3 seconds in total since the default interval is 500ms return new WebDriverWait driver  timeout  Until d   gt         var e   driver FindElement By Id someId        if  e Location    prevLocation                stationaryCount            return stationaryCount    desiredStationarySamples             prevLocation   e Location      stationaryCount   0      return false

User · Answer

This is caused by following 3 types   1 The element is not visible to click   Use Actions or JavascriptExecutor for making it to click   By Actions   WebElement element   driver findElement By  element path      Actions actions   new Actions driver    actions moveToElement element  click   perform      By JavascriptExecutor   JavascriptExecutor jse    JavascriptExecutor driver   jse executeScript  scroll 250  0        if the element is on top   jse executeScript  scroll 0  250        if the element is on bottom    or  JavascriptExecutor jse    JavascriptExecutor driver   jse executeScript  arguments 0  scrollIntoView     Webelement      Then click on the element   2 The page is getting refreshed before it is clicking the element   For this  make the page to wait for few seconds   3  The element is clickable but there is a spinner overlay on top of it  The below code will wait until the overlay disppears  By loadingImage   By id  loading image ID     WebDriverWait wait   new WebDriverWait driver  timeOutInSeconds    wait until ExpectedConditions invisibilityOfElementLocated loadingImage      Then click on the element

User · Answer

Explanation of error message   The error message simply says  that the element you want to click on is present  but it is not visible  It could be covered by something or temporary not visible   There could be many reasons why the element is not visible in the moment of the test  Please re-analyse your page and find proper solution for your case   Solution for particular case   In my case  this error occures  when a tooltip of the screen element i just clicked on  was poping over the element I wanted to click next  Defocus was a solution I needed    Quick solution how to defocus would be to click to some other element in another part of the screen which does  nothing  resp  nothing happens after a click action   Proper solution would be to call element blur   on the element poping the tooltip  which would make the tooltip disapear

User · Answer

I had same exception while trying to click one of the radio buttons on my page  I used below Javascript and exeted using IJavaScriptExecutor   C  example  string script   function clickCharity        var InputElements   document getElementsByName  Charity         for  i 0  i lt InputElements length  i            if InputElements i  getAttribute  value       true                       InputElements i  click                         var js WebDriver as IJavaScriptExecutor  js ExecuteScript script

User · Answer

I had another bug where find link on Chrome and Poltergeist could not click an A tag with an EM tag and some text inside of it  although it worked fine in Firefox and rack test  The solution was to replace click link link  with   find  a em   text  link  click

User · Answer

Re Tony L  mpada s answer  comment  27 did indeed solve the problem for me  except that it provided Java code and I needed Python  Here s a Python function that scrolls to the element s position and then clicks 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     This solved the problem for me in Chrome 34 0  It caused no harm in Firefox 28 0 and IE 11  those browsers aren t subject to the problem  but scrolling to the element s position before clicking it still isn t a bad thing

User · Answer

I was facing the same problem with clj-webdriver   clojure port of Selenium   I just translated the previous solution to clojure for convenience  You can call this function before doing click or whatever to avoid that problem    defn scrollTo    Scrolls to the position of the given css selector if found     q     if  exists  q        let   loc  location-once-visible q  jscript  str  window scrollTo     x loc        y loc                 execute-script jscript

User · Answer

I  too  wrestled with this problem  Code works fine in FF  fails on Chrome  What I was trying to do was to click a tickbox - if it wasn t in view  I d scroll to view and then click  Even scrolling into view works in Chrome  only the bottom few pixels of the tickbox wasn t visible so webdriver refused to click on it    My workaround is this   WebElement element    sectorPopup findElement          Locatable  element  getCoordinates   inViewPort    try       element click      catch  Exception e        new Actions getWebDriver    sendKeys Keys PAGE DOWN  perform        element click        Chrome also has issues with sendKeys  using Actions is sometimes necessary  Obviously  you need to know which direction and how much you need to go so your mileage may vary  But I prefer this to the javascript hack  so I m posting it here in case someone else will find it useful

User · Answer

It s funny  all the time I spent looking at the various responses  no one had tried the obvious  which of course  I hadn t either  If your page has the same id used multiple times  as mine did    newButton    and the one you want is not the first one found  then you will in all likelihood get this error  The easiest thing to do  C     var testIt   driver FindElements By Id  newButton       Note it s FindElements  not FindElement   And then test to see how many results came back from the retrieval  If it s the second one  you can then use   testit 1  Click      Or get whomever reused ids to fix them

User · Answer

I had the same issue  tried all offered solutions but they did not work for me  eventually I used this   JavascriptExecutor js    JavascriptExecutor  driver  js executeScript  var evt   document createEvent  MouseEvents        evt initMouseEvent  click  true  true  window  0  0  0  0  0  false  false  false  false  0 null       arguments 0  dispatchEvent evt     findElement element      Hope this helps

User · Answer

In Visual Studio 2013  if you enable BrowserLink - it displays a BrowserLink navbar at the bottom of the screen  If the item you want to click is behind that navbar  it give the error  Disabling BrowserLink solved the problem for me

User · Answer

I was getting this error when running tests headless with xvfb-run  They were working flawlessly locally  Using chrome  versions of webdriver   chromedriver   chrome   java etc all identical   The    won   t fix    bug in chromedriver - GitHub Link pointed out by Tony L  mpada suggested this may be related to what is   isn t visible on the screen   Help message for xvfb-run shows the following   -s ARGS   --server-args ARGS    arguments  other than server number and                                  -nolisten tcp   to pass to the Xvfb server                                  default   -screen 0 640x480x8     Changing the resolution for xvfb made the error go away   xvfb-run -s  -screen 0 1280x1024x16

User · Answer

Apparently this is the result of a  quot Won t Fix quot  bug in the Chrome driver binary  One solution that worked for me  Our Mileage May Vary  can be found in this Google Group discussion  Comment  3  https   groups google com forum  fromgroups   topic selenium-developer-activity DsZ5wFN52tc The relevant portion is right here   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  quot    quot    GetAttribute  quot href quot      In my case  I m using Python  so once I got the desired element  I simply used driver get ViewElm get attribute  href     I would expect this to only work  however  if the element you are trying to click on is a link

User · Answer

ruby watir-webdriver chrome  I use the following trick and seems like it works    scroll to myelement  browser execute script  window scrollTo   myelement element wd location 0     myelement element wd location 1        click myelement myelement when present fire event  click

User · Answer

If you are having this issue with a modal  pop-up   note that it may be that another element with the same properties exists underneath the current top level modal  This caught me out  just increase the specificity of your selector to reduce the scope to that of the modal you are trying to click only

User · Answer

I made this method based on a comment from Tony L  mpada s answer  It works very well      def scroll to element    page execute script  window scrollTo   element native location x     element native location y     end

User · Answer

I was also stuck for two days because of the same reason  actually Scrolling will make it work  because may be the data couldn t load properly  which may cause the same error again and again   What I did is  I scroll down randomly   once with  0 -500   then  0 400   then  0 -600   you may give these scroll value according to your use  Just scroll it where you have the content to click   driver execute script  scrollBy 0 -500     sleep 5   driver execute script  scrollBy 0 400     sleep 5   driver execute script  scrollBy 0 -600     sleep 5    It really worked

User · Answer

I was getting the same issue while running selenium script in python  Here is what I used to click on the element   from selenium webdriver common action chains import ActionChains   ActionChains driver  click element  perform

User · Answer

I was having this exact issue when clicking a button within an Angular Material menu  Whenever I clicked a button inside a menu  the  cdk-overlay-pane would receive the click  The solution is to increase the z-index of buttons inside the menu   cdk-overlay-pane button     z-index  1001

User · Answer

If you have jQuery loaded on the page  you can execute the following javascript command            element id       click      Example using python executor   driver execute script       s   click      element id

User · Answer

You can also use JavaScript click and scrolling would be not required then   IJavaScriptExecutor ex    IJavaScriptExecutor Driver  ex ExecuteScript  arguments 0  click      elementToClick

User · Answer

First  try to get the latest Chrome driver and check if it solves the issue    In my case  it didn t fix the issue  But  the following solution worked for me so far  The following is C  code but you can follow same logic in your specific language  What we do here is    Step 1  Focus on the element using the Selenium Actions object   Step 2  Then do a click on the element  Step 3  If there s an exception  then we trigger a javascript  Click  event on the element by executing the javascript script through the Selenium browser driver s  ExecuteScript  method    You can also skip step 1 and 2 and try only step 3 too  Step 3 would work on it s own but I noticed some strange behavior in one scenario in which step 3  even though it successfully clicked the element  caused unexpected behavior in other parts of my code after clicking the element               try                                 Setup the driver and navigate to the web page                    var driver   new ChromeDriver  folder path to the Chrome driver                    driver Navigate   GoToUrl  UrlToThePage                       Find the element                    var element   driver FindElement By Id  elementHtmlId                         Step 1                 new Actions driver  MoveToElement element  Perform                         Step 2                 element Click                              catch  Exception                                  Step 3                 driver ExecuteScript  document getElementById  elementHtmlId   click

User · Answer

I was facing a similar problem whre i have to check two check boxes one after the other But i was getting the same above error hence i added wait in between my steps for checking the checkboxes    its working fine and great here are the steps -    When I visit  administrator user profiles   And I press xpath link       id  1      Then I should see  Please wait for a moment       When I wait for 5 seconds   And I press xpath link       id  2      Then I should see  Please wait for a moment       When I visit  administrator user profiles updates

User · Answer

I ran into this problem and it seems to be caused  in my case  by clicking an element that pops a div in front of the clicked element   I got around this by wrapping my click in a big  ol try catch block

User · Answer

I have seen this in the situation when the selenium driven Chrome window was opened too small  The element to be clicked on was out of the viewport and therefore it was failing   That sounds logical    real user would have to either resize the window or scroll so that it is possible to see the element and in fact click on it   After instructing the selenium driver to set the window size appropriately this issues went away for me  The webdriver API is decribed here

User · Answer

In Drupal when using Selenium          Get element       element    this- gt driver- gt getElement  xpath   input                   Get screen location       location    element- gt getLocation           To make sure that Chrome correctly handles clicking on the elements         outside of the screen  we must move the cursor to the element s location       this- gt driver- gt moveCursor  location  x     location  y             Optionally  set some sleep time  0 5 sec in the example below  if your        elements are visible after some animation      time nanosleep 0  500000000           Click on the element       element- gt click

User · Answer

This might help someone who is using WebdriverIO   function        var runInBrowser   function argument             argument click               var elementToClickOn   browser    element        browser execute runInBrowser  elementToClickOn       Source   https   www intricatecloud io 2018 11 webdriverio-tips-element-wrapped-in-div-is-not-clickable

User · Answer

In Rselenium  this happened with code successfully used many times when a link was positioned at the top window border  Simple solution was to use sendKeysToElement   as follows   if  unlist webElem isElementDisplayed           webElem sendKeysToElement list key    up arrow       Add  up arrow        webElem clickElement          before  clickElement

User · Answer

I do a kind of brute force of clicks and it works for me   try      elem click   except      print  failed to click      size   elem size     mid of y   int size  height    2     stepts to do to left   int size  width        while stepts to do to left  gt  0          try              print stepts to do to left  mid of y             action   webdriver common action chains ActionChains driver              action move to element with offset elem  mid of y  stepts to do to left              action click               action perform               print  DONE CLICK              break         except              pass

User · Answer

I had the same problem and it was caused by an id conflict between the div and the link inside the div  So driver was clicking on the div instead of the link that I wanted  I changed the div id and it worked properly   Before    lt div id  logout  gt  lt a id  logout  href  logoutLink  gt logout lt  a gt  lt  div gt    After    lt div id  differentId  gt  lt a id  logout  href  logoutLink  gt logout lt  a gt  lt  div gt

User · Answer

I am facing the same issue and I used delay and it is working fine my side  Page was getting refresh and getting the other locators   Thread sleep 2000           Click By xpath       id  instructions container   a

User · Answer

I met this because a loading dialog cover on this element  I simplely solve it by add a waiting before working with the this element    try           Thread sleep  int   3000          catch  InterruptedException e                       e printStackTrace            Hope this help

User · Answer

Maybe it s not really clean solution but it works   try      el click   except WebDriverException as e      if  Element is not clickable at point  in e msg          self browser execute script                   sel    click    format sel el selector                else          raise

User · Answer

When using Protractor this helped me   var elm   element by css   your-css-class     browser executeScript  arguments 0  scrollIntoView      elm getWebElement     elm click

User · Answer

I had the same problem and spent hours in finding the solution  I tried to click a cell at the bottom of a long ngGrid using protractor  Here is a snapshot of my ngGrid html       many rows here    lt  - row in renderedRows - gt      lt  - column in renderedColumns - gt      lt div     gt   lt a ngclick  selectRow row      gt the test link 100000 lt  a gt            all clicking function did not work  The solution is to use evaluate in the element s current scope   element by cssContainingText  a    the test link 100000         evaluate  selectRow row

[google-chrome] Debugging "Element is not clickable at point" error

Examples related to google-chrome

Examples related to selenium

Examples related to selenium-webdriver

Examples related to automated-tests