1673266 - Unable to save to PDF using new print UI

Status: RESOLVED WORKSFORME

(Core :: Print Preview, defect, P2)

Description

[Sean Voisen (:svoisen)]

As of the latest Nightly (84) on macOS I'm now unable to save anything to PDF using the "Save to PDF" destination in the new print UI. Clicking "Save" causes the tab modal to briefly flicker, but nothing happens. Old UI continues to work as expected.

Will attempt to run mozregression.

Comment 1

[Sean Voisen (:svoisen)]

No regression found with mozregression. Something must be wrong with my print settings. I cloned my profile and in the clone clicked the new "Clear saved print settings" button, which fixed the issue.

FWIW, here are the Save to PDF settings from about:support prior to nuking them with the clear button:

print.printer_Mozilla_Save_to_PDF.print_bgcolor	false
print.printer_Mozilla_Save_to_PDF.print_bgimages	false
print.printer_Mozilla_Save_to_PDF.print_duplex	0
print.printer_Mozilla_Save_to_PDF.print_edge_bottom	0
print.printer_Mozilla_Save_to_PDF.print_edge_left	0
print.printer_Mozilla_Save_to_PDF.print_edge_right	0
print.printer_Mozilla_Save_to_PDF.print_edge_top	0
print.printer_Mozilla_Save_to_PDF.print_evenpages	true
print.printer_Mozilla_Save_to_PDF.print_footercenter	
print.printer_Mozilla_Save_to_PDF.print_footerleft	
print.printer_Mozilla_Save_to_PDF.print_footerright	
print.printer_Mozilla_Save_to_PDF.print_headercenter	
print.printer_Mozilla_Save_to_PDF.print_headerleft	
print.printer_Mozilla_Save_to_PDF.print_headerright	
print.printer_Mozilla_Save_to_PDF.print_in_color	true
print.printer_Mozilla_Save_to_PDF.print_margin_bottom	0.5
print.printer_Mozilla_Save_to_PDF.print_margin_left	0.5
print.printer_Mozilla_Save_to_PDF.print_margin_right	0.5
print.printer_Mozilla_Save_to_PDF.print_margin_top	0.5
print.printer_Mozilla_Save_to_PDF.print_oddpages	true
print.printer_Mozilla_Save_to_PDF.print_orientation	0
print.printer_Mozilla_Save_to_PDF.print_page_delay	50
print.printer_Mozilla_Save_to_PDF.print_paper_height	11
print.printer_Mozilla_Save_to_PDF.print_paper_id	na_letter
print.printer_Mozilla_Save_to_PDF.print_paper_name	A4
print.printer_Mozilla_Save_to_PDF.print_paper_size_unit	0
print.printer_Mozilla_Save_to_PDF.print_paper_width	8.5
print.printer_Mozilla_Save_to_PDF.print_resolution	0
print.printer_Mozilla_Save_to_PDF.print_reversed	false
print.printer_Mozilla_Save_to_PDF.print_scaling	1
print.printer_Mozilla_Save_to_PDF.print_shrink_to_fit	true
print.printer_Mozilla_Save_to_PDF.print_to_file	true
print.printer_Mozilla_Save_to_PDF.print_to_filename	/Users/svoisen/Desktop/YouTube Player Demo | YouTube IFrame Player API | Google Developers.pdf
print.printer_Mozilla_Save_to_PDF.print_unwriteable_margin_bottom	0
print.printer_Mozilla_Save_to_PDF.print_unwriteable_margin_left	0
print.printer_Mozilla_Save_to_PDF.print_unwriteable_margin_right	0
print.printer_Mozilla_Save_to_PDF.print_unwriteable_margin_top	0

The most recent settings architecture change on macOS is bug 1667053. jfkthame: Does anything stand out to you? Not sure why it says A4 paper but 8.5x11 for width and height.

Comment 2

[Jonathan Kew [:jfkthame]]

I don't see anything that immediately strikes me as odd there. The discrepancy between print_paper_id and print_paper_name worried me for a moment, until I remembered that we don't read or write print_paper_name at all these days; that's just an obsolete pref you happen to have hanging around, but nothing looks at it. (That changed a month ago, in bug 1665904.)

Maybe we should also look at the non-driver-specific print prefs, in case there's something weird there.

Comment 3

[Sean Voisen (:svoisen)]

Attachment: about:support

Comment 4

[Jonathan Kew [:jfkthame]]

Hmm, one thing that strikes me as odd there is the different forms of pathname/URL in the *.print_to_filename prefs of various destinations. But I believe the unadorned path (as in the print.printer_Mozilla_Save_to_PDF.print_to_filename setting) is the right thing, so I don't know why it wasn't working for you.

Comment 5

[Sean Voisen (:svoisen)]

Now I can't reproduce this since updating to a newer Nightly build on the profile where it was broken. Will keep this open, but still not sure what happened.

Comment 6

[Sean Voisen (:svoisen)]

I suspect this was fixed in a newer Nightly; I still can't reproduce so I'll just close it and reopen if it happens again.