Steps to Reproduce: 1. open an URL 2. confirm that a UI element (a button in my case) is visible (optional step) 3. click on it Actual result: safaridriver does not click on an element Expected result: safaridriver clicks on an element Specs: macOS Catalina Version 10.15.3 Safari Version 13.0.5 (15608.5.11) STP Release 100 (Safari 13.2, WebKit 15610.1.2.1)
<rdar://problem/59483073>
W3C element click tests have not recently regressed, and so, we cannot reproduce this issue locally without more information. Please provide the following information: """ Include versions of Selenium or other WebDriver client libraries, Safari, safaridriver, macOS. Describe the failing command and its inputs and outputs and include diagnostics collected after running the test. (You can enable safaridriver diagnostics by passing --diagnose to safaridriver or via other methods, see the instructions for this in `man safaridriver`.) Did this behavior occur in a previous release of Safari? Does this behavior occur in other browsers (Firefox, Chrome, Edge)? What language is the test written in? Do you use Selenium Grid, SauceLabs, BrowserStack, or other scaling infrastructure? If possible include a Webarchive of the page as it was when the command failed, a test page accessible to us, and the test case itself. """ If you cannot share this information publicly on bugzilla, then please file a report at https://feedbackassistant.apple.com/.
@Brian Burg, With some research I found out that safaridriver does click on an element with .click() method, but it does click below an element (reference: https://github.com/SeleniumHQ/selenium/issues/7649). And the only workaround for now is to use driver.executeScript('arguments[0].click()', element); Do you have plans to fix the issue with .click() method in near future? Thank you for you time!
@Brian Burg The click occurs by 39 pixels below. Maybe your regression tests have target elements with height bigger than 80 pixels.
(In reply to Brian Burg from comment #2) > W3C element click tests have not recently regressed, and so, we cannot > reproduce this issue locally without more information. Please provide the > following information: > > """ > Include versions of Selenium or other WebDriver client libraries, Safari, > safaridriver, macOS. > > Describe the failing command and its inputs and outputs and include > diagnostics collected after running the test. (You can enable safaridriver > diagnostics by passing --diagnose to safaridriver or via other methods, see > the instructions for this in `man safaridriver`.) > > Did this behavior occur in a previous release of Safari? > Does this behavior occur in other browsers (Firefox, Chrome, Edge)? > What language is the test written in? > Do you use Selenium Grid, SauceLabs, BrowserStack, or other scaling > infrastructure? > > If possible include a Webarchive of the page as it was when the command > failed, a test page accessible to us, and the test case itself. > """ > > If you cannot share this information publicly on bugzilla, then please file > a report at https://feedbackassistant.apple.com/. Hi Brian, I have a reproducible test case at https://github.com/matthew-horrocks/WebkitFailure Using crossbrowsertesting.com. Steps in the test: 1. webpage is loaded, CLICK ME link is clicked Expected outcome: The text CLICKED is displayed Actual outcomes: Mac OSX 10.15, Safari 13 Failing test The text CLICKED is not displayed. Passing test Mac OSX 10.14, Safari 12 The text CLICKED is displayed. Matt
The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'. This should now be fixed in shipping software.