Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

map/area Element is not clickable in Chrome, but works in other browsers #2750

Closed
lukeis opened this issue Mar 3, 2016 · 13 comments
Closed

Comments

@lukeis
Copy link
Member

lukeis commented Mar 3, 2016

Originally reported on Google Code with ID 2750

I have a page than has an element:
<map>
   <area onclick="bot_flightOnly();return false;" alt="Flight Only" href="javascript://
Flight Only" coords="3,3,79,29" shape="rect">
</map>

Clicking on the "area", produces the following error in Chrome:
Caught: org.openqa.selenium.WebDriverException: Element is not clickable at point (0,
0). Other element would receive the click: <div id="MAINSHELL">...</div>

See attached sample test. It is written in Groovy, and you will need to provide your
own chromedriver binary.

I am running on Linux i386, Selenium 2.10.0, chromedriver 16.0.902.0

Reported by mark.lehky on 2011-11-01 21:39:29


- _Attachment: [SampleMapTest.groovy](https://storage.googleapis.com/google-code-attachments/selenium/issue-2750/comment-0/SampleMapTest.groovy)_
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by dawagner on 2011-11-02 05:12:53

  • Labels added: Component-WebDriver, Browser-Chrome

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Even I was getting this issue.But this element was newly created element as a result
of previous step and hence refreshing the browser (driver.get(url)) and then performing
element.click resolved the issue.

Reported by pavithra.krishna@teamaol.com on 2011-11-23 06:17:58

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

My element is always there - not new. But just in case I tried driver.get(driver.getCurrentUrl())
right before the problem click(), and still same problem.
Thanx for the offer though.

Reported by mark.lehky on 2011-11-23 15:45:12

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I have also seen this bug.  It happens only when driving Chrome.  Firefox 7.0.1 has
no problem clicking the same checkbox.  This element is always on the page so the suggestion
of driver.get(url) did not solve my problem.

The section of script which is failing is very simple:

driver.find_element(:id, "bAddReceipt").click



Here is the html and css for the relevant element:

.checkbox input, .radio input {
    position: absolute;
}
.checkbox label, .radio label {
    padding: 0 0 0 22px;
    position: relative;
    top: 3px;
}
<div class="checkbox">
<input id="bAddReceipt" class="CheckboxInput" type="checkbox" value="1" name="bAddReceipt">
<label for="bAddReceipt">Use Detailed Add Receipt</label>
</div>

Reported by Tracey.Ruark on 2011-12-02 15:04:26

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I have a similar issue with SmartGWT pages.
SmartGWT buttons apparently are not really <input> tags, which is why I believe the
chromedriver fails on "element is not clickable. Another element '<td>....' would get
the  click.
This simple click does work perfectly in FF8 and IE8

Reported by stevendegroote on 2012-01-06 12:58:11

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by kkania@google.com on 2012-01-12 19:19:55

  • Status changed: Accepted

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

I also have this issue. GWT has rendered an input field like this:

<div class="...">
    <input type="text" id="username" name="username" autocomplete="on" tabindex="1"
placeholder="Email address">
    <div class="gwt-Label ..."/>
</div>

However, the div.gwt-Label element is rendered completely covering the input field.
This makes it impossible to click on the input field, e.g. to clear any placeholder
text before sending keys.

Firefox 14 and IE9 have no such problem.

Reported by rankincj on 2012-08-17 09:26:33

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

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)

Reported by ch.sreehari on 2013-04-16 07:07:39

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Are you reading the topic and the original report?
This issue is related to map/area support only.

Reported by barancev on 2013-04-16 07:23:31

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by barancev on 2013-04-16 07:25:58

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by kkania@google.com on 2013-04-19 15:52:05

  • Status changed: Accepted

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Moved to: Issue chromedriver:319

Reported by kkania@google.com on 2013-04-19 15:52:06

  • Status changed: Moved

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by luke.semerau on 2015-09-17 18:14:00

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 3, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant