[🐛 Bug]: There seems to be some confusion in the ChromiumDriver when checking the CDP version.

[666asd]

What happened?

In the ChromiumDriver.java file of Selenium, the check for the CDP version is performed using the originalCapabilities, while the logging statement utilizes the capabilities.

How can we reproduce the issue?

I'm unsure about the intended usage of either originalCapabilities or capabilities in this specific context of checking the CDP version in ChromiumDriver. However, if you wish to specify the version of selenium-devtools by specifying the BrowserVersion in capabilities, you may achieve that.

Relevant log output

七月 24, 2023 4:20:06 下午 org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
警告: Unable to find CDP implementation matching 115
七月 24, 2023 4:20:07 下午 org.openqa.selenium.chromium.ChromiumDriver lambda$new$3
警告: Unable to find version of CDP to use for 110. You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.8.1` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's.

Operating System

all

Selenium version

java

What are the browser(s) and version(s) where you see this issue?

all

What are the browser driver(s) and version(s) where you see this issue?

all

Are you using Selenium Grid?

No response

[github-actions]

@666asd, 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]

The content is the same for the code purpose. I made an update to use the same variable.

[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.