[dotnet] Hide unnecessary chromium public fields

[nvborisenko]

This pull request makes a small but important change to the ChromiumDriver class by changing the visibility of several static fields from public to protected. This limits their accessibility to the class itself and its subclasses, rather than exposing them publicly.

• Changed the visibility of the following static fields from public to protected in ChromiumDriver.cs:
  • AcceptUntrustedCertificates
  • ExecuteCdp
  • GetCastSinksCommand
  • SelectCastSinkCommand
  • StartCastTabMirroringCommand
  • StartCastDesktopMirroringCommand
  • GetCastIssueMessageCommand
  • StopCastingCommand
  • GetNetworkConditionsCommand
  • SetNetworkConditionsCommand
  • DeleteNetworkConditionsCommand
  • SendChromeCommand
  • SendChromeCommandWithResult
  • LaunchAppCommand
  • SetPermissionCommand

💡 Additional Considerations

Hopefully nobody even knows it exists. So just "remove".

🔄 Types of changes

• Cleanup (formatting, renaming)
• Breaking change (fix or feature that would cause existing functionality to change)

[qodo-code-review]

PR Type

Enhancement

---

Description

• Reduce public API surface by hiding internal Chromium fields

• Change 15 static fields from public to protected visibility

• Prevent external code from depending on internal implementation details

---

File Walkthrough

Relevant files

Enhancement

ChromiumDriver.cs Reduce public API surface for Chromium driver                        dotnet/src/webdriver/Chromium/ChromiumDriver.cs Changed visibility of 15 static readonly fields from public to protected Fields include command constants and configuration flags used internally Maintains functionality while reducing public API surface Affects: AcceptUntrustedCertificates, ExecuteCdp, GetCastSinksCommand, SelectCastSinkCommand, StartCastTabMirroringCommand, StartCastDesktopMirroringCommand, GetCastIssueMessageCommand, StopCastingCommand, GetNetworkConditionsCommand, SetNetworkConditionsCommand, DeleteNetworkConditionsCommand, SendChromeCommand, SendChromeCommandWithResult, LaunchAppCommand, SetPermissionCommand +15/-15

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[Copilot]

Pull request overview

This PR reduces the public API surface of the .NET ChromiumDriver by changing several command-name/static fields from public to protected, limiting access to subclasses (e.g., ChromeDriver, EdgeDriver) rather than all consumers.

Changes:

• Changed multiple ChromiumDriver static fields (command names and AcceptUntrustedCertificates) from public to protected.

[drauch]

We're using SendChromeCommand to clear all cookies in all domains via "Network.clearBrowserCookies". How is this to be done going forward?

Best regard,
D.R.

[nvborisenko]

@drauch

chrome.ExecuteCdpCommand("Network.clearBrowserCookies", []);

[drauch]

Ah, it looked like ExecudeCdpCommand was obsoleted as well.

[nvborisenko]

Ah, it looked like ExecudeCdpCommand was obsoleted as well.

still actual:

selenium/dotnet/src/webdriver/Chromium/ChromiumDriver.cs

Line 294 in 384a286

public object? ExecuteCdpCommand(string commandName, Dictionary<string, object?> commandParameters)