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
fix: honor pageRanges when printing #25064
Conversation
1eb4c8e
to
6d008c7
Compare
ccf6f05
to
f40eac9
Compare
53974f1
to
a436c2c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested this PR on Windows 10 with the sample code at https://gist.github.com/0c1c8affb9262ae83bde4d08d3401f0c and the ranges are working as expected 👍
Note about the screenshot: the Windows screenshot reads "1-3" rather than "1-4" as in e.g. the Linux screenshot, but there are indeed only 3 pages on Windows and so the pageRange is correct.
Release Notes Persisted
|
@codebytere has manually backported this PR to "10-x-y", please check out #25597 |
@codebytere has manually backported this PR to "11-x-y", please check out #25600 |
Description of Change
Closes #25013.
The print ranges in Chromium's print job settings were not being properly
plumbed through to various platforms' UI through the correct codepaths.
This fixes that by setting them should they exist.
Upstream CL open at https://chromium-review.googlesource.com/c/chromium/src/+/2380886
On macOS
On Linux
On Windows
Tested with https://gist.github.com/0c1c8affb9262ae83bde4d08d3401f0c.
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where pageRanges was not properly honored when printing.