Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

printing in chrome on ios 10 fails when pdf was loaded by blob #8934

Closed
grd2345 opened this issue Sep 19, 2017 · 1 comment
Closed

printing in chrome on ios 10 fails when pdf was loaded by blob #8934

grd2345 opened this issue Sep 19, 2017 · 1 comment
Labels

Comments

@grd2345
Copy link

grd2345 commented Sep 19, 2017

Link to PDF file (or attach file here):

Configuration:

  • Web browser and its version: chrome 61.0.3163.73
  • Operating system and its version: ios 10
  • PDF.js version: 1.9.575
  • Is an extension: no

Steps to reproduce the problem:

  1. Just load a pdf from blob in the viewer
  2. Click print button

What is the expected behavior? (add screenshot)
Expecting the print preview menu to open up containing the pdf.

What went wrong? (add screenshot)
After printing progress, nothing opens up.

Notes:
I was debugging this and the issue seems to be something in pdf.js after the viewer calls pdfPage.render(renderContext).promise under function renderPage the scratchCanvas.toDataURL() doesn't return the string representation of the image. I tested this in all other platforms like Safari, chrome on desktop, chrome on android and the scratchCanvas.toDataURL() return the string representation of the page canvas and renders fine, but seems in chrome ios 10, this is not occurring.

@Snuffleupagus
Copy link
Collaborator

I tested this in all other platforms like Safari, chrome on desktop, chrome on android and the scratchCanvas.toDataURL() return the string representation of the page canvas and renders fine, but seems in chrome ios 10, this is not occurring.

Given that this is specific to a particular platform/browser, it seems to point to a browser bug rather than a PDF.js one; should this issue be closed as INVALID since there's probably not much to be done here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants