-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
[bug] firefox version > 47 + Gecko driver + browserstack #1539
Comments
it seems that it concerns only browser stack. |
Update :
|
it concerns only browser stack firefox version <= 47. |
firefox version > 47 need marionette (gecko driver). By default, selenium is in 2.x version and don't need a gecko driver in browserStack |
it seems that the problem occured with browserstack firefox version between 48 and 58. Waiting firefox 59 version to test. Problem is due to mouseToMoveToElement is not suported yet by gecko. Click, key press and double clic use mouse See SeleniumHQ/selenium#3808 |
@ryltar , we still need to better handle the error message to make it clear that it failed to find the element. |
The problem of click which is transformed into a wait is solved by using an Action object like selenium docs say. I don't have yet push on github On browserStack firefox only, keypress, double click and click are not working due to firefox version. Selenium say that MouseMouveTo operation is not supported but it seems that in firefox 59, this problem is solved. Retrying click with a loop will not solved the problem because of MouseMouveTo A little workaround trick is to set the version of firefox to 47 It's a very stange problem because on my localhost, i tried with the same gecko , selenium and firefox version and all action are supported Maybe just a problem with browserstack firefox. |
Hello,
There is a unexpected issue in one of the Cerberus campaign. We have one action set to 'click' on a element selected using xpath :
But running this campaign, this action seems to be executed as a 'wait' :
The xpath selection doesn't seem to cause any problem but the click is not done which make the following steps fail.
Any ideas ?
Thanks
The text was updated successfully, but these errors were encountered: