1668228 - Print Preview to take by default the document's title for the Print to PDF option

Status: RESOLVED INVALID

(Core :: Printing: Setup, enhancement)

Description

[Catalin Sasca, Desktop QA [:csasca]]

Attachment: Title enh.png

Affected versions

• Firefox 82.0b5
• Firefox 83.0a1

Affected platforms

• Windows
• macOS
• Ubuntu

Steps to reproduce

1. Launch Firefox
2. Access a page of choice
3. Access print preview
4. Select "Print to PDF" as destination
5. An OS menu will appear asking the user to rename the pdf document before saving it.

Expected result

• The title of the document is taken from the actual document and autofilled in "Name" by default.

Actual result

• The "Name" column is empty and the user needs to input a name before saving the document

Additional notes

• This will be faster for users who are not interested in the name of the document, and will automatically take it's default name.
• The title and the empty "file name" can be seen in the attachment

Comment 1

[Sean Voisen (:svoisen)]

Unable to reproduce on macOS in Nightly 83. Will attempt on Windows. If this is true, then this would seem to be a regression since this was working at some point.

Comment 2

[Jonathan Watt [:jwatt]]

You don't link to it in this bug, but I believe you're testing with http://www.dbsparks.com/research/html/SNRN02.pdf

Like Sean, this works for me in latest Nightly on macOS, and also in latest Beta. Bob, maybe you can test this on Windows?

Comment 3

[Jonathan Watt [:jwatt]]

I just noticed that your screen capture shows that "Microsoft Print to PDF" is selected. That pseudo-printer invokes the "Save As..." dialog itself and we have no control over what name is pre-populated in that dialog. If you try in Edge and Chrome you will notice that they also do not pre-populate the filename for that pseudo-printer.

Testing our own "Save to PDF" pseudo-printer on Windows 10, it pre-populates the filename dialog just fine in Nightly.

Since it looks like you mistakenly tested Microsoft's pseudo-driver instead of ours it looks like this bug is invalid (can't fix). Please reopen if that's not the case.