New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repeated hover does't work #1507
Comments
Could you please attach a trace-level log from geckodriver? Read more about reporting actionable bugs in our contribution guidelines. |
Trace-level log has been attached. |
There are tons of execute script calls in that log. Please create a minimized testcase best without any JS framework, or Javascript involved which still reproduces this problem. A trace log from such an execution would be good to have. |
@whimboo The JS is the Selenium isDisplayed JS atom, there are no other JS libraries required, it can basically be ignored for the purpose of that trace log. |
I can confirm this issues exists in version 0.24.0
Here is trace log for working hover action (first one):
And this one failed to hover (second one):
EDIT: This might be Firefox version related issue, it works fine on Firefox 63.0.1 and 64.0.2 |
this may be the same issue i sent to the selenium users google group at https://groups.google.com/forum/#!topic/selenium-users/JYJKHUa0hdM my focus (really hover) issues began with Firefox 65. 64.0 worked fine. 65.0.2 32-bit works fine. 65.0.2 64-bit does not. @acikojevic did you by chance try Firefox 65 32-bit to see if that works? if it does, i think our issues are identical. |
Firefox 66.0, 64-bit, has the same problem |
@whimboo is there still reporter feedback you are looking for on this one or is @acikojevic 's trace log sufficient? |
@snowymike we are currently limit in doing work on geckodriver, sorry. So any additional feedback from you and others would be welcome. Given that 64 was working for you, it would be good to know when during the Firefox 65 development process the issue started for you. Maybe you could check the beta versions of Firefox and tell me in which of those it started for you? It would make it easier to pinpoint the underlying change. Those builds can be found at http://archive.mozilla.org/pub/firefox/releases/. |
@whimboo i'll try to narrow down which 65 beta broke things. i just tried 66.0.1 today, focus still messed up there. |
it's broken in the first 65 beta i see at that link, 65.0b3, http://archive.mozilla.org/pub/firefox/releases/65.0b3/win64/en-US/ it was tricky to avoid auto-update happening. unchecking the Mozilla Maintenance service during install wasn't enough to block it. i ended up unchecking launch firefox at install completion, such that the first run of firefox was through geckodriver, as the way to keep the version at 65.0b3. |
Mind also testing the devedition releases which would be beta 1 and 2? You can find those here: https://archive.mozilla.org/pub/devedition/releases/ This seems to be similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1538486. |
beta 1 also broken |
@whimboo any other info that would be helpful for me to provide? |
not fixed in 66.0.3 either. any update on this issue? i haven't seen anything new posted here or at https://bugzilla.mozilla.org/show_bug.cgi?id=1538486 in the last month. |
Sorry, but I'm currently working on a different project. So I don't have the time to follow on all the bugs/issues for geckodriver. What would be necessary now is a regression test based on Nightly versions of Firefox. That would help us to pinpoint the change in behavior to a single day, and that might indicate which change caused it. Based on the release calendar Firefox 65 was on mozilla-central from 2018-10-22 to 2018-12-10. A bisect for those builds would be necessary. Would you mind doing that? We have a tool called mozregression where you could automate that, or you can use mozdownload to grab specific versions of Firefox Nightly. Thanks! |
i'll need something i can run on windows. looking at the mozregression and mozdownload links you sent, i'm not certain how precisely i'd get an installer for 64-bit windows for a certain date. if you can share the commands for how i'd get, for example, a 2018-11-10 build of Firefox 65 for 64-bit windows, i'll give it a shot. |
@snowymike Direct downloads of older nightlies can be found at https://archive.mozilla.org/pub/firefox/nightly/2018/ , but automating the regression test should save you a lot of clicking through installers and stuff 😉. There's a windows installer for mozregression as documented at https://mozilla.github.io/mozregression/install.html , and there's a quick start video tutorial at https://mozilla.github.io/mozregression/quickstart.html |
In the case you don't want to use mozregression, for mozdownload just use |
it's broken in the very first nightly build of 65 it works properly in the final nightly build of 64 |
Thanks a lot @snowymike! Now lets move further investigation to the before-mentioned bug. |
i don't have a bugzilla account to post it there, but fyi, the moz:useNonSpecCompliantPointerOrigin setting discussed at https://bugzilla.mozilla.org/show_bug.cgi?id=1538486 does avoid the focus problem in my test. @whimboo would you mind reporting that there? i added this one line
to my existing method below
and that worked in Firefox 66.0.5 64-bit Windows |
Thanks! I will add a comment on the bug for that. |
Since this bug was laying around for a while and users were forced to set the @snowymike, @acikojevic or @insight do you still run into it with |
Actually I was able to reproduce it with a Firefox 78 build. More testing revealed that this issue is gone since the Firefox 84 release. For more details see https://bugzilla.mozilla.org/show_bug.cgi?id=1538486. |
@whimboo so no need for
in builds 84 or newer, correct? |
@snowymike yes that would be correct. I would appreciate if you could test your specific example(s) and report back. Thanks! |
@whimboo sorry for the delay i find i still need the workaround in version 112 of Firefox, 64-bit, on Windows 11. i first confirmed things didn't work with geckodriver 0.30.0, 64-bit, Windows, then tried the latest, 0.33.0 and have the same issue. the tests we have that focus on a text input in order to dismiss a popover in another part of the screen, that initially started failing in Firefox with version 65, do not work without the workaround of:
|
Hi @whimboo , This is still broken as of Firefox 119 and geckodriver 0.33.0. Additionally, the workaround using the above capability no longer works because it is no longer supported as of version 116. So currently, versions 116 and later are not testable on my end because many of my tests perform multiple hovers on the same element. The only workaround I have for now is to remain on version 115, which isn't a great long term solution. Any additional attention to this issue would be greatly appreciated. |
@jeremy-of-laurel would you mind filing a new issue for it and if possible attaching a testcase that could be used to reproduce - maybe even with some lightweight HTML? Note that we were asking via various channels if anyone is still using this capability but we didn't get any reply. As such we decided to remove it due to no known problems with the WebDriver API. When you provided the details we can clearly have a look. |
FYI I'm aware this is semi-ancient. But I've found a similar use case. I was originally directed after googling a bug for capybara and found this. teamcapybara/capybara#2156 I think "part" of the issue, is that chrome hovering works differently (It seems), to firefox. I've been discussing in #selenium on slack to see if the issue boils down to your "current" focus point being identical to the requested "hover point" Firefox: v121 Can I ask whimboo that If I am "on" element A, i.e. it's highlighted in the background. But no dropdown is there, should hovering on element A be permissible. It is on chrome that is also running locally with latest versions. EDIT: I am not using any special capabilities. I am also not able to reliably share the html (As it is behind a login wall). The problem is demonstrable if you have a dropdown that requires a hover, and it is "highlighted" (Through maybe some other means). A rudimentary image of my situation is below Because it has some sort of "latent" state, |
Any news on this @whimboo - Could we get this re-opened as this has regressed? |
@luke-hill would you mind filing a new issue for your problem? Also a minimized HTML with such a dropdown would be kinda helpful. |
Hi @whimboo - I'm not sure how easy it is to replicate a minimized html file. I will however file a new issue. |
System
Testcase
I found this bug in capybara test:
This case reproduced in https://gist.github.com/lnsight/1440b63dd3fbbaf4c612a0714342f66b
Stacktrace
Trace-level log
https://gist.github.com/lnsight/4dfcce03fe3c700a8f146d2570409338
The text was updated successfully, but these errors were encountered: