1502636 - click on Imagemap throws "element not interactable" exception

Status: NEW

(Remote Protocol :: Marionette, defect, P5)

Description

[Alexei Barantsev]

Attachment: trace.log

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce:

Run this code using Selenium client (Java binding):

driver.get("https://output.jsbin.com/gegatap");
driver.findElement(By.id("rectG")).click();


Actual results:

400 Bad Request {"value":{"error":"element not interactable","message":"Element <area id=\"rectG\" href=\"https://www.seleniumhq.org/projects/\"> could not be scrolled into view" ...

Trace log attached.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

This only fails for clicks when having the webdriver compat mode enabled. The reason is that the <map> element is basically not visible but overlays the specified image reference, and as such doesn't appear in the paint tree.

As such the check should be performed against the referenced image but not the `area` or `map` element.

Andreas, I wonder if this would need an extension of the WebDriver spec, because nothing really specializes image maps there yet.

Comment 2

[Andreas Tolfsen ❲:ato❳]

Yes, this is a known bug with algorithm that’s currently set out
in the specification.

barancev: If you could file an issue against the specification when
you have time that would be great.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Andreas Tolfsen ⦗:ato⦘ from comment #2)

barancev: If you could file an issue against the specification when
you have time that would be great.

Hi Alexei, did you have the time for that already? If yes, can you please us know about the issue?

Comment 4

[Alexei Barantsev]

Submitted: https://github.com/w3c/webdriver/issues/1411