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
Navigating to a valid but unreachable domain is not an error #770
Comments
We clearly pass step 5 and started a navigation as it can be seen in the trace log. But given that the URL is not reachable Firefox displays an error page. As such we hit step 9-1 for the So why should this result in a success and not error? |
@shs96c any feedback regarding my last comment? |
@whimboo we have the same issue. The problem is on older Firefox like 45, when navigating to an invalid url, it will not throw an exception. But on gecko, the situation is different so that our existing test cases will all fail. Is there any way restoring back to the same behavior as older Firefox? |
Well, I don't see it as a problem when checking the current webdriver spec. So we need feedback from @shs96c here. I'm also cc'ing @andreastt and @AutomatedTester in case they are faster with a reply. |
The remote server is the thing that's having a problem and tells people this via the status code, but the navigation itself succeeds. |
So what about the post navigation checks?
Why is that then not a network error? |
A network error in this context isn't an OSI layer 7 error, but happening lower in the stack. Examples would include TCP/IP timeouts, connections not being completed, and so on. |
Would you mind making this clearer in the webdriver spec? Right now it misses any details and leaves up enough space for interpretation. |
I can make that clear. w3c/webdriver#1009 |
Any solved yet? I'm still facing this issue. |
In order to help us efficiently investigate your issue, please provide the following information:
Platform and application details
Steps to reproduce
It is expected for the driver to return a value of success with a value of null, as per the Go Command spec. The URL is valid and absolute, so we should pass the check in step 5.
Reproducable testcase:
See above
A trace level log:
The text was updated successfully, but these errors were encountered: