-
-
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]: Upgrading to WebDriver 4.2.0 throughs false positive validateCapability failures while initializing a new session #10711
Comments
@MohabMohie, 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! |
I'm guessing we need to differentiate between what the user sets and what Java is helpfully setting for the user. |
Thank you for reporting this, it seems we add some caps in the response which should not need to be added. But there are also a few ChromeDriver adds to the response which are not W3C (e.g. I am having a look at this now. |
Created a ChromeDriver issue for the invalid |
Issue created for Firefox/GeckoDriver mozilla/geckodriver#2023 |
Pushed a fix and will do a patch release soon, between today and tomorrow. |
And for MSEdgeDriver MicrosoftEdge/EdgeWebDriver#23 |
and temporarily excluding some non W3C caps from checks since they are returned by browser drivers. Fixes SeleniumHQ#10711
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?
When I initialize a new chromeDriver instance with a specific chromeOptions object, several false-positive failure logs are thrown telling me that certain capabilities (that I'm not using) are not W3C compliant and I should remove them.
Expected: only relevant capabilities that I'm actually using should trigger such messages.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 11
Selenium version
Java 4.2.0
What are the browser(s) and version(s) where you see this issue?
Chrome 101
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 101.0.4951.41
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: