Created attachment 400573 [details] webdriver returns - true for isDisplayed() and for isEnabled() In case link or button or any other element which is clickable located inside of <footer> html element - webElement.click() -does not work correct -> there is no exception just nothing. In case to perform the click on element using JS -> it works. I've supposed it's some issue in Project code , but I checked this functionality on github.com and apple.com websites - result the same - after click() on the such elements - nothing happens Please see attachments and just so simple code just for checking public static void main(String[] args) { WebDriver webDriver = new SafariDriver(); webDriver.get("https://www.apple.com/tv/"); webDriver.findElement(By.xpath("//footer//a[@href = '/mac/']")).click(); // u can add this line here to have time to see or use debug mode as I --- Thread.sleep(10000); webDriver.quit(); } Mac OS 10.15.4, 10.15.5 Safari version 13.1 SeleniumWebDriver - 3.14 (last stabled) Code based Java 8
This occurs when the element is located off-screen when the page loads; click() works fine for elements that are already on screen but if it requires scrolling, it will scroll but not click. Here's a full example demonstrating this: public static void main(String[] args) { WebDriver driver = new SafariDriver(); driver.manage().window().fullscreen(); driver.get("https://github.com/SeleniumHQ/selenium/issues?q=safari"); driver.findElement(By.cssSelector("a[data-ga-click='Footer, go to help, text:help']")).click(); System.out.println("Expected: 'https://help.github.com/'\nActual : '" + driver.getCurrentUrl() + "'"); driver.close(); }
(In reply to f-gu from comment #1) > This occurs when the element is located off-screen when the page loads; > click() works fine for elements that are already on screen but if it > requires scrolling, it will scroll but not click. This sounds exactly like a bug addressed in <https://bugs.webkit.org/show_bug.cgi?id=208232>. Please try using Safari Technology Preview 109+, Safari 14 betas, or the macOS Big Sur beta to verify it's been fixed. *** This bug has been marked as a duplicate of bug 208232 ***