Using "Pages per sheet" option results in graphics incorrectly scaled for some PDFs
Categories
(Core :: Printing: Output, defect)
Tracking
()
People
(Reporter: haik, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
When printing some PDFs on macOS, using the Pages per sheet
option to print multiple pages of the document on one sheet, the resulting output PDF has images that are not scaled correctly.
The attached image is a screenshot showing the difference between the print preview dialog showing the correct scaling and the generated PDF when Pages per sheet
is set to 2. In the output PDF (previously saved), the images are scaled too large.
The PDF used in the attachment is available here.
Hit on macOS 13 Beta 7 (22A5342f). Firefox 104.02.
Reproduces on macOS 10.14.6 also.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:alaskanemily, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 2•2 years ago
|
||
Thanks for reporting this! I was not able to reproduce this on my machine, I will ping someone to test on OS X.
I'm wondering if this is related to bug 1755974
Can you check if this still occurs after ensuring that pages-per-sheet in the system dialog is set to 1 and the zoom level is set to 100%?
Does it occur when using a clean profile? You can create a new clean profile to use to test (and switch back to your original profile afterwards) using the instructions here: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
Comment 3•2 years ago
|
||
This might actually be Bug 1779202 , can you update to the current Firefox version and test? That bug was fixed in 105 (which is the current release version), but was still an issue in 104.
Reporter | ||
Comment 4•2 years ago
|
||
(In reply to Emily McDonough [:alaskanemily] from comment #3)
This might actually be Bug 1779202 , can you update to the current Firefox version and test? That bug was fixed in 105 (which is the current release version), but was still an issue in 104.
Sounds right. The bug is not reproducible for me on 105, but it is still reproducible on 104.02.
And running $ ./mach mozregression --find-fix --bad 104 --good 106
yielded this pushlog which includes bug 1779202 and one other unrelated change.
I'll close this as a dupe of 1779202.
Thanks!
Updated•2 years ago
|
Description
•