[🚀 Feature]: [Selenium Manager] User should have option to fallback to previous stable version of browser driver

[saiparth]

Feature and motivation

Thanks for adding selenium manager.
One request is, sometimes latest version of chromedriver may have some issues. Previous version of driver may work with latest version of chrome. hence rather than having blocked, User should be able to specify fallback option so that selenium will download previous stable version.
Ex:
Chrome 106 and Chromedriver 106 - Timed out receiving message from renderer
Chrome 106 and Chromedriver 105 - works fine

Thanks

Usage example

I should be able to specify browser driver version or Boolean flag to fallback to previous stable version while initializing browser.

[github-actions]

@saiparth, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

That is a feature that we need to double check because it is not a common case but for now you can always set the location of your driver, as Selenium Manager is a fallback for now.

@titusfortner @bonigarcia thoughts?

[bonigarcia]

I had never heard about this need. Although technically, it is possible to use the previous stable version of a given browser with Selenium Manager, I think this is not the best approach.

Selenium Manager uses the recommended driver version for a given browser. For instance, for Chrome 106, the official chromedriver version should be 106.0.5249.61 (see the chomedriver download page). If chromedriver 106.x has some problem that does not happen in version 105.x, maybe it is worth reporting it (see chomedriver contributing page).

[diemol]

I think that is a good point, and in any case, I believe we won't change the interface drastically when Selenium Manager is the default in Selenium, users should be able to set the location of the driver.

[titusfortner]

This is a legit use case in either direction (newer or older versions).
The Selenium Manager already supports this, but the bindings do not.

This will give the location of that driver regardless of the browser version.

selenium-manger --browser chrome --driver-version 106.0.5249.61

The languages need to provide access to this functionality, though.

We should discuss how we want users to pass this info in for future versions of Selenium, I don't think we need to wait for it to be the default implementation to get this to work.

[titusfortner]

I think how we do this will be determined by #11353.
If there is any specific outcomes from this one, please provide input there.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.