1669365 - BUG REPORT 81.0.1 (64 BIT) Firefox does not permit printing to any installed PDF app. Will not work with NuancePDF or native PDF in Windows.

Status: RESOLVED INCOMPLETE

(Core :: Printing: Output, defect, P2)

Description

[jwllwj]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

Attempt to Print webpage to a pdf

Actual results:

Attempt to print webpage to a .PDF page fails. Select the .pdf app to print to and the printing does not occur. The page does not print at all. No result.

Expected results:

Page should have printed to a .pdf document.

Comment 1

[Emilio Cobos Álvarez (:emilio)]

Can you attach your about:support information please?

Comment 2

[Emilio Cobos Álvarez (:emilio)]

Also, does it work with a clean profile? See https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

Comment 3

[jwl]

I made a new profile and the bug did not occur.

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Ok, that's a bit of a relief... but still, can you attach the information that you get in about:support? I suspect you have some print prefs set that may be causing problems.

Thanks!

Comment 5

[Jonathan Watt [:jwatt]]

Unfortunately printing prefs are blacklisted from about:support in v81. If bug 1666956 get's uplifted to beta we'll have them in about:support in v82 once it's released in 10 days or so. Otherwise the prefs can be obtained by going to about:support, clicking the button in the "Profile Folder"/"Profile directory" row to open the profile directory, opening the prefs.js file, and copying and pasting all lines containing "print." along with the line containing "print_printer" and pasting them here (preferably as an attachment using the Attach New File button above).

Comment 6

[jwl]

Sorry, the bug continues even with the new profile.

Regarding the last comment above: does that mean the problem will be fixed in the next release?

Otherwise, the workaround is to do the printing from Chrome (this worked well although I prefer Firefox).

Comment 7

[Boris Chiou [:boris]]

Set S1 because this is a P1 bug for now. (Hope the next release provides the workaround way or just fix this.)

Comment 8

[Jonathan Watt [:jwatt]]

jwl, Firefox 82 is out now. Can you update firefox to the latest release, double check that this issue is still happening for you. If so, can you open the page about:support, click on the "Copy text to clipboard" button, come back to this bug report and click "Attach new file", and then paste and submit the copied text?

Comment 9

[jwllwj]

Updated to Firefox 82.0. Problem continues in Firefox 82.0 (64-bit) – no different. Not able to print to a PDF printer.

Thank you for continued attention to this bug and for informing me about any progress to fix this bug.

William

Comment 10

[Sean Voisen (:svoisen)]

Hi William: Can you open the URL about:support, click on the "Copy text to clipboard" button, come back to this bug report and click "Attach new file", and then paste and submit the copied text? Please do this with Firefox version 82. That may help us diagnose the issue.

Comment 11

[jwl]

You instructed me to
"...open the URL about:support, click on the "Copy text to clipboard" button, come back to this bug report and click "Attach new file", and then paste and submit the copied text? Please do this with Firefox version 82. That may help us diagnose the issue."

There is no (or I cannot find) the "about:support"
When i go to the About Firefox it displays a pop-up box without any support option. Please be more specific and detailed about how to get to the item to which you are referring.
Thank you

Comment 12

[Emilio Cobos Álvarez (:emilio)]

type about:support in the url bar

Comment 13

[Jonathan Watt [:jwatt]]

jwl: to clarify what Emilio said, you'd type "about:support" into the location/URL bar to get to the Support page, just as you might type in "bugzilla.mozilla.org" to get to this website.

I'm going to close this as "incomplete" for now since we haven't had a response from you yet, but we can reopen this bug if the issue is still happening for you and you can provide the extra requested information.