You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[🐛 Bug]: [dotnet] Null check on ISupportsPrint.Print is different from parameter name #14784
@RenderMichael, 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.
This is caused by a mismatch in parameter names between the interface ISupportsPrint.Print(options) and the implementing type WebDriver.Print(printOptions). This is considered incorrect (for reasons such as this one) but fixing it directly is a breaking change. We can do something like this:
This would throw an exception with the right parameter name, whether a user goes through the interface or the type. We can factor out the double null-check if that's desired.
Edit: Default Interface Methods are not supported on .NET Standard 2.0, so this could only be applied to .NET 8.
Let's fix it, selenium doesn't follow SemVer. To negotiate this "minor" breaking change we will reflect this change in Blog post (automatically will be included).
If we create a commit something like [dotnet] [breaking change] printOptions parameter name in Print method renamed to options, then it is enough. And, of course, reflect it in CHANGELOG when releasing.
Activity
github-actions commentedon Nov 20, 2024
@RenderMichael, 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-templatelabel.If the issue is a question, add the
I-questionlabel.If the issue is valid but there is no time to troubleshoot it, consider adding the
help wantedlabel.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 answerlabel.Thank you!
RenderMichael commentedon Nov 21, 2024
This is caused by a mismatch in parameter names between the interface
ISupportsPrint.Print(options)and the implementing typeWebDriver.Print(printOptions). This is considered incorrect (for reasons such as this one) but fixing it directly is a breaking change. We can do something like this:This would throw an exception with the right parameter name, whether a user goes through the interface or the type. We can factor out the double null-check if that's desired.
Edit: Default Interface Methods are not supported on .NET Standard 2.0, so this could only be applied to .NET 8.
nvborisenko commentedon Dec 1, 2024
Let's fix it, selenium doesn't follow SemVer. To negotiate this "minor" breaking change we will reflect this change in Blog post (automatically will be included).
If we create a commit something like [dotnet] [breaking change]
printOptionsparameter name inPrintmethod renamed tooptions, then it is enough. And, of course, reflect it in CHANGELOG when releasing.Delta456 commentedon Dec 20, 2024
This PR can be closed as #14773 is merged which fixes it.
github-actions commentedon Jun 18, 2025
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.
github-actions commentedon Dec 16, 2025
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 14 days.
github-actions commentedon Jun 16, 2026
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 14 days.
github-actions commentedon Jul 1, 2026
This issue was closed because it has been stalled for 14 days with no activity.
github-actions commentedon Jul 31, 2026
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.