1789573 - PDF viewer doesn't catch cmd+p

Status: RESOLVED INACTIVE

(Toolkit :: Printing, defect)

Description

[Janne P]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

Open pdf in pdf viewer
Push CMD+P to print

MacOS Sierra 10.12.6

Actual results:

Instead of printing pdf as is, the print is website containing the pdf.js viewer showing only the first page of file, as if you would select print command from file menu.

Expected results:

Printing the pdf as is the same way you would get if you press the print button in the pdf viewer.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jfkthame, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[Jonathan Kew [:jfkthame]]

More of a Toolkit issue than Core::Printing: Output, I think.

Comment 4

[Mark Striemer [:mstriemer]]

Hi Janne,

How are you opening the PDF viewer? Is this from a website, a local file, or something else?

I'm seeing the same results between Ctrl+P (Windows), and from a file:// URL.

Thanks!

Comment 5

[Janne P]

PDF is generated on server and opened by a script in new window but instead going to new background tab per settings(http://kb.mozillazine.org/Browser.link.open_newwindow)

(In reply to Mark Striemer [:mstriemer] from comment #4)

Hi Janne,

How are you opening the PDF viewer? Is this from a website, a local file, or something else?

I'm seeing the same results between Ctrl+P (Windows), and from a file:// URL.

Thanks!

Comment 6

[Mark Striemer [:mstriemer]]

Is the webpage the PDF document itself or is it being embedded with an <object> tag or manually loaded in PDF.js or something else? I still cannot reproduce