1360348 - .pdf printing messed up

Status: RESOLVED INVALID

(Firefox :: PDF Viewer, defect)

Description

[clint]

Attachment: print.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170413192749

Steps to reproduce:

using the latest version of firefox (53.0 32bit windows 10) with the native, built-in .pdf viewer within firefox... I attempted to print a .pdf file and the spacing of the font is all messed up.






Actual results:

see screenshot. http://i.imgur.com/oczG7BE.jpg
The text characters are too close to on another. Some letters are even touching 


Expected results:

a proper, normal print-out of the .pdf file.  I have to say, it seems the native, built-in firefox .pdf viewer/printer is awful.

Last month, printing something with the built-in firefox .pdf viewer was awful (see this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1349616 )  

at least that bug seems to have been resoled. but now a new one has taken it's place.

Comment 1

[Loic]

Link to PDF?

Comment 2

[b.bellec]

Hello,

Can you check the status of the Firefox Multiprocess mode (aka e10s) in about:support ?

If it's enabled, disable the multiprocess mode. To do so, go to about:config, look for "tabs.remote" entries and set all of them to false. Restart Firefox and retry to visualize your PDF.

Comment 3

[clint]

I can try this suggestion, but what does multiprocess mode do, and how would it effect the rest of the web browser? 
 I'd hate to have to disable/enable this every time i wanted to print a .pdf
I hope eventually there is a better solution than this.

Comment 4

[Brendan Dahl [:bdahl]]

Can you provide a link or attach a PDF with this issue?

Comment 5

[Brendan Dahl [:bdahl]]

Closing, still haven't received any more info.

Comment 6

[clint]

(In reply to Brendan Dahl [:bdahl] from comment #5)
> Closing, still haven't received any more info.

it is the same issue as the one here  https://bugzilla.mozilla.org/show_bug.cgi?id=1349616

Comment 7

[Brendan Dahl [:bdahl]]

(In reply to clint from comment #6)
> (In reply to Brendan Dahl [:bdahl] from comment #5)
> > Closing, still haven't received any more info.
> 
> it is the same issue as the one here 
> https://bugzilla.mozilla.org/show_bug.cgi?id=134961

With the PDF from that issue you can still reproduce the problem with Firefox 56?