[🐛 Bug]: [dotnet] Print range does a no-op on single value requests

[RenderMichael]

What happened?

Requesting a range to print does not work when asking for a single page. No exception is thrown, no page is added to the request.

How can we reproduce the issue?

var options = new PrintOptions();
options.AddPageRangeToPrint("1");
driver.Print(options);

Relevant log output

N/A

Operating System

Windows 11

Selenium version

.NET nightly

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

N/A

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

N/A

Are you using Selenium Grid?

No

[github-actions]

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

Thank you!

[nvborisenko]

We have

.AddPageToPrint()
.AddPageRangeToPrint

The question what is expected behavior when we call: .AddPageRangeToPrint("1"). I have no strong opinion, but I prefer to not touch it )

[RenderMichael]

The two options are AddPageRangeToPrint("1") -> AddPageToPrint(1), or an exception. I would prefer the first one, but I can see either one.

[nvborisenko]

My opinion is:
"1" is not a range. "1 -3" is a range. Given that we have 2 separate methods, then we should distinguish it. Each method should be responsible for specific cases and not be "universal". I really want to not touch it.

Let us to focus on BiDi implementation: https://github.com/SeleniumHQ/selenium/blob/trunk/dotnet/src/webdriver/BiDi/Modules/BrowsingContext/PrintCommand.cs - soon BiDi will be a primary underlying mechanism to interact with browser, I propose to focus more on this rather on "years working" mechanism.

[github-actions]

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.