-
Notifications
You must be signed in to change notification settings - Fork 324
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
Unable to find element on selenoid/firefox while the element can be found on selenoid/chrome #890
Comments
@fedika Selenoid just does reverse proxying to geckodriver inside Docker image. So just the same issue should reproduce locally with Firefox 74.0 and latest Geckodriver release if you go there directly: run Geckodriver manually as a binary and then go to |
hi @vania-pooh , Thanks for response, but I did not find same issue when run locally use geckodriver v1.19.1 and Firefox 74.0, the element can be found. Here is the log from selenoid:
based on the log above, why did the server keep call until 1,51? this is the log that I got from selenium-debug.log locally use geckodriver and firefox |
@fedika we are using Geckodriver 0.26.0 in latest Firefox images. |
Hello @vania-pooh and selenoid team, thank you so much all your work. I'm currently having the same issue as Fedika. I've a sample here https://github.com/grasspine/selenoid-nightwatch-test |
@fedika @grasspine could you try to open tested page in Selenoid UI and make sure that the element you are trying to find actually appears? Couldn't this element be platform-specific (Selenoid is running browsers in Linux Docker containers)? |
@vania-pooh yes, the element appears in Selenoid UI and it doesn't seem to be a platform specific element since it's a search bar in duckduckgo page. Next I tried finding 'body' and it resulted in the same error.
Updated the sample. |
Hai @vania-pooh and selenoid teams. Thanks for your hard work I used Ubuntu 18.04.4 LTS, Docker 19.03.8, Nightwatch 1.3.4 and Nightwatch-api 3.0.1. This error that I've received:
Can you look into it? Thank you |
@farcyn what you are showing is a normal Geckodriver log. Could you share an exact error message you are getting? |
@vania-pooh this error that I've received after I acces https://mobile.twitter.com/login and tried click the forgot password button |
@farcyn according to the log Geckodriver successfully returns found element ID. |
it returns the same result when running locally but here it's working fine.
|
with selenoid
full log: https://codeshare.io/5OyWbg |
Any updates on this? Our team is facing the same issue. |
@cjgratacos what I'm trying to say for 2 years already, this is not a Selenoid bug. Selenoid just proxies everything to Geckodriver. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Dear selenoid,
Thank you for provide selenoid as test environments, I'm really appreciate it.
So far we use selenoid, selenoid_ui and selenoid/vnc_chrome and there is no problem with them when we run the tests.
But when we try to run our tests on selenoid/vnc_firefox, the browser opened up, page displayed but all of elements cannot be found, whild we do not face this problem on selenoid/vnc_chrome.
The spec :
selenoid v1.10.0
selenoid_ui v1.10.0
selenoid/vnc_firefox:70.0
I tried to run our tests on webdriver local firefox version 74 and it works.
Thank you
The text was updated successfully, but these errors were encountered: