-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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 NuGet package not updated with newer CDP bindings #10583
Comments
@jeffreyrivor, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
4.1.1 was released earlier today which supports recent CDP versions. |
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?
The Selenium.WebDriver 4.1.0 NuGet package is several major releases behind the stable Chrome DevTools Protocol, so it does not work with latest stable of Chrome (v100.x as of this writing). The latest version in 4.1.0 release is v96 which is no longer works against v100. The .NET bindings are clearly being kept updated as the CDP is versioned (see https://github.com/SeleniumHQ/selenium/commits/trunk/dotnet/src/webdriver/DevTools) but no NuGet package releases have been made.
It seems to me that there should be a new 4.x.x release of the Selenium.WebDriver NuGet package based on the latest trunk.
How can we reproduce the issue?
Operating System
Windows Server 2022
Selenium version
.NET 4.1.0
What are the browser(s) and version(s) where you see this issue?
Chrome 101.0.4951.15
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 101.0.4951.15
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: