1121009 - error in PDF.JS (viewer.js) with self-printing PDFs

Status: RESOLVED INCOMPLETE

(Firefox :: PDF Viewer, defect, P3)

Description

[Will Sullivan]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36

Steps to reproduce:

I've got a repro website with more details, including some results from debugging viewer.js

http://firefoxselfprintingpdfbug.azurewebsites.net/

Using the built-in PDF viewer (pdf.js, configured via Options -> Applications -> Portable Document Format(PDF) : Preview in Firefox), and attempted to open a self-printing PDF. 


Actual results:

The user gets a dialog that states "there was an unexpected problem while printing".


Expected results:

The user should have been presented the print dialog.  If you install the Mozilla Labs pdf.js plugin https://addons.mozilla.org/en-US/firefox/addon/pdfjs/ it works as expected.  Something is happening in viewer.js during normal execution that can't be observed while debugging.  If you visit the above website you can read more and repro it for yourself.

Comment 1

[Will Sullivan]

Just updated to 35.  Bug still exists, and now the pdfjs addon isn't available.  Joy.

Comment 2

[Loic]

It regressed indeed. To reproduce it, after cliking on the link, you can scroll fastly the pop-up window when the PDF is loading.
I think it's a bug about rendering the PDF contents.

regression range:
good=2014-06-17
bad=2014-06-18
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=bb35d1b73634&tochange=37f08ddaea48

Ryan VanderMeulen — Bug 1025878 - Update pdf.js to version 1.0.370. r=yury

Maybe that patch:
#4941 Prevent rendering unnecessary pages when the HOME/END keys are pressed

Comment 3

[Brendan Dahl [:bdahl]]

Appears to only happen on windows.

Comment 4

[Jonas Jenwald [:Snuffleupagus]]

(In reply to Will Sullivan from comment #0)

I've got a repro website with more details, including some results from
debugging viewer.js

http://firefoxselfprintingpdfbug.azurewebsites.net/

Given that the website is no longer available, and that the user account is disabled, closing as INCOMPLETE for now.
If this issue still occurs, and an updated example link is provided, this bug can be re-opened.