Closed tjwelde closed 7 years ago
This is a duplicate of https://github.com/mozilla/geckodriver/issues/875, and it’s a Selenium issue.
So you are saying, the getWindowRect endpoint gets called wrongfully by selenium? But why does it work with FF 55?
Well that specifically is hard to tell because you didn’t include a trace-level log from geckodriver, like you were asked to in the issue template. But generally, a mapping error between types means Selenium isn’t up to date with the WebDriver standard.
@andreastt, do we really support 52.0ESR with geckodriver 0.18? I thought the minium version for it is 54.0?
@whimboo The recommended minimum version is indeed 54. This is clearly laid out in the README (my highlights):
Support is best in Firefox 54 and greater, although generally the more recent the Firefox version, the better the experience as they have more bug fixes and features. Some features will only be available in the most recent Firefox versions, and we strongly advise using the latest Firefox Nightly with geckodriver. Since Windows XP support in Firefox was dropped with Firefox 53, we do not support this platform.
Alright, so @goldquest has to pick a release of geckodriver which supports the 52.0ESR release branch.
@andreastt could we get a document started (maybe here in the wiki) which lists which version of geckodriver is supposed to work for which releases of Firefox. This would help a lot when checking compatibility for older Firefox releases. Right now this is not obvious.
@goldquest picked up Firefox 55 in #892 (comment), but I so far have no indication what’s wrong with getting the window rect from that version as we’re missing a trace-level log.
@whimboo This is off-topic, but since we don’t have any exhaustive testing against previous release channels I’m hesitant to set in stone which Firefox versions we support. For as long as geckodriver is pre-release software, Firefox support is going to be a little hit and miss as we adapt to the WebDriver protocol. Fortunately, the protocol will be frozen from next Thursday, which will make life easier for us as implementors.
@goldquest picked up Firefox 55 in https://github.com/mozilla/geckodriver/issues/892#issuecomment-324151016, but I so far have no indication what’s wrong with getting the window rect from that version as we’re missing a trace-level log.
He said that this version is working correctly. That's why my comment regarding a backward-incompatible feature change in a geckodriver release later than the supported for 52.0.
All in all what should be done here is to downgrade geckodriver. Maybe then getWindowRect
will not be present. If that's the case an upgrade of Firefox would have to be done.
But why does it work with FF 55?
My bad, I misread a “not” into this sentence.
Removing label Selenium
given that it's a compat issue.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue.
System
Testcase
on mac:
Now you can run your webdriver commands.
dockerhost
is the domain name for the host.This is the scenario, I am trying to solve, but I also tested with a local selenium and FF and it also didn't work, with the same error.
Stacktrace