#1903 Incorrect behaviour for DomElement.click() method

[Anton]

Hi,

Since v2.25 behaviour for DomElement.click() method has been changed and now it is different in comparsion with real browsers. Seems that there is extra visibility check which is not required.

Please find the patch with test for exposing this problem and removing extra validation.

[Ahmed Ashour]

Test cases added in SVN.

The only change:

assertEquals(URL, URL) instead of (String, URL)

[Anton]

Any updates on this issue?

[RBRi]

Hi Anton,
sorry for comming back that late to this issue. Have done some debugging and it looks like a bug in the HtmlUnit Driver. Do you use the driver or pure HtmlUnit?

[Anton]

Thanks for a response, I will double check it and provide more details later

[RBRi]

looks like we have some more problem here. Working on more test cases at the moment and will fix it after that.

[Anton]

Thanks

[Anton]

Do you need help with investigation or additional tests writing?

[Atsushi Nakagawa]

Thanks RBRi. I think the fixes for #1939 are definitely improvements and solves the problem for Javascript, but what about DomElement.click() which still has visibility check?

Should these two lines of code behave differently? First still has visibility check as at trunk @ r15041 while second doesn't.

p.<HtmlElement>getFirstByXPath("//area[@id='a1']").click();

p.executeJavaScript("document.getElementById('a1').click()");

Personally, I think visibility check at this layer makes HtmlUnit difficult to use, and feels kind of superflous because application code is already at a stage where it's decided it wants to click it, regardless of (or despite of) visibility.