-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
[🐛 Bug]: Update .NET API Docs #10126
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
Comments
@JonathonAnderson, 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, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
This issue is stale because it has been open 280 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 14 days with no activity. |
The root issue here is bazel limitations in .NET |
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 available stable API version for C# is 4.1.0, but when I open the docs and navigate to the ChromeDriver section, the content is for version 3.1.0. This was exceptionally confusing for me as numerous methods have been removed, but they are listed in the docs, so I couldn't figure out why the methods were not available.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10
Selenium version
4.1.0
What are the browser(s) and version(s) where you see this issue?
Chrome 96.0.4664
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 96.0.4664
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: