Closed TatuLund closed 7 months ago
This was easy to replicate, but the root cause of the problem was less obvious. I just by accident noticed that how Chrome reports browser name has changed and it uses different string with headless mode and non-headless. Hence correct action is to fix isChrome method to work as this problem could be wider than just CheckBoxElement
@TatuLund can we close this issue as the referenced PR has been merged already?
@mshabarov sure, I thought it was autoclosed already.
Vaadin 8, TestBench 5.2.0:
CheckboxElement.click() method with Chrome 121+ is now throwing the following except
org.openqa.selenium.ElementClickInterceptedException - element click intercepted: Element is not clickable at point (631, 146). Other element would receive the click:
After working with Javier we found that this did work
checkBox.getCommandExecutor().executeScript("arguments[0].click()", checkBox.getInputElement());