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]: Selenium Manager not getting Chromium version number #11884
Comments
And, never mind, it is an issue of how Ruby is parsing the JSON output... |
Ok, so, the debug info from Ruby is showing an empty response, but the json output from executing from the command line:
So, probably a Ruby issue, but only in Windows? but maybe something in Rust? |
Ah, I see, the backslashes need to be escaped again for Windows |
@p0deje should we just replace: with:
|
@titusfortner Do we need to pass the binary file path as |
Forward slashes do not work:
The
|
No, 4.8.3 does not work either. I'm testing with an older version of Chromium that doesn't work with the latest chromedriver. Selenium Manager uses the latest driver by default, which means it might work by accident. |
@titusfortner How do you make it work from CLI? I cannot seem to find a combination of slashes that would actually work for me:
|
Umm, not sure command line, do you need to escape anything? In Ruby, I got this working: |
Can you try making it work from CLI in Windows? |
What I'm trying to figure out is whether we should fix it in Rust code rather than escaping in all bindings if it doesn't work from CLI. |
Ideally the escaping should be done by the tool that start the process? Like, blank spaces was the issue we saw in SeleniumConf. |
Yes, it would probably be preferable, I'm just not sure what's the proper slashes combination we should support on Windows. |
I committed what worked for me. Should be good enough for 4.9. |
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. |
What happened?
Trying to use a chromium implementation instead of Chrome. I believe this feature is currently only implemented in Ruby.
Finally got it tested on Mac and it is working, so just a Windows issue.
How can we reproduce the issue?
options = Selenium::WebDriver::Options.chrome(binary: 'C:\chrome-win\chrome.exe') driver = Selenium::WebDriver.for :chrome, options: options
Relevant log output
Operating System
Windows 11
Selenium version
Ruby 4.8.6
What are the browser(s) and version(s) where you see this issue?
Chromium 107
What are the browser driver(s) and version(s) where you see this issue?
n/a
Are you using Selenium Grid?
n/a
The text was updated successfully, but these errors were encountered: