This method does not work on Chrome (causing the AppVeyor build failures after merging #7586), and is sometimes unreliable on Firefox too. Use AppPage's click method instead, which uses JavaScript and is reliable across both browsers.
Haha I don't know how unreliable is WebElement#click but using Javascript's click would mean that it's not really a UI test, e.g. we can happily use it to click even when something is off screen (though I am aware of the catches/limitations of Selenium so sometimes we have to use such workarounds).
I am just wondering is this the best option though? If there is a way to get WebElement#click to work we should prefer it, otherwise it is not a UI Test.
@LiHaoTan allow me to give you the deal breaker: https://stackoverflow.com/questions/38923356/element-is-not-clickable-at-point-other-element-would-receive-the-click.
@wkurniawan07 Are you suggesting using maximize()?
We already used that, evidently with limited success.
Most helpful comment
We already used that, evidently with limited success.