pdfjs-dist

7255 Commits

1 Branch

1804 Tags

126 MiB

Tree: a2e8a5ee7f

Commit Graph

Author	SHA1	Message	Date
Rob Wu	1731c0fb42	Add mozPrintCallback shim This shim does the following: 1. Intercept window.print() 2. For a window.print() call (if allowed, ie. no previous print job): 1. Dispatch the beforeprint event. 2. Render a printg progress dialog. 3. For each canvas, call mozPrintCallback if existent (one at a time, async). 4. During each mozPrintCallback callback, update the progress dialog. 5. When all <canvas>es have been rendered, invoke the real window.print(). 6. Dispatch the afterprint event. The shim is not included in Firefox through the preprocessor. Keyboard shortcuts (Ctrl/Cmd + P) are intercepted and default behavior (i.e. printing) is prevented, and the steps for window.print() are run. window.attachEvent is used, in order to cancel printing in IE10 and earlier (courtesy of Stack Overflow - http://stackoverflow.com/a/15302847). Unfortunately, this doesn't work in IE11 - if Ctrl + P is used, the print dialog will be shown twice: Once because of Ctrl + P, and again when all pages have finished rendering. This logic of this polyfill is not specific to PDF.js, so it can also be used in other projects. There's one additional modification in PDF.js's viewer.js: The printed <canvas> element is wrapped in a <div>. This is needed, because Chrome would otherwise print one canvas on two pages.	12 years ago

Author

SHA1

Message

Date

Rob Wu

1731c0fb42

Add mozPrintCallback shim

This shim does the following:
1. Intercept window.print()
2. For a window.print() call (if allowed, ie. no previous print job):
   1. Dispatch the beforeprint event.
   2. Render a printg progress dialog.
   3. For each canvas, call mozPrintCallback if existent (one at a time, async).
   4. During each mozPrintCallback callback, update the progress dialog.
   5. When all <canvas>es have been rendered, invoke the real window.print().
   6. Dispatch the afterprint event.

The shim is not included in Firefox through the preprocessor.

Keyboard shortcuts (Ctrl/Cmd + P) are intercepted and default behavior
(i.e. printing) is prevented, and the steps for window.print() are run.
window.attachEvent is used, in order to cancel printing in IE10 and
earlier (courtesy of Stack Overflow - http://stackoverflow.com/a/15302847).
Unfortunately, this doesn't work in IE11 - if Ctrl + P is used, the
print dialog will be shown twice: Once because of Ctrl + P, and again
when all pages have finished rendering.

This logic of this polyfill is not specific to PDF.js, so it can also
be used in other projects.

There's one additional modification in PDF.js's viewer.js: The printed
<canvas> element is wrapped in a <div>. This is needed, because Chrome
would otherwise print one canvas on two pages.

12 years ago

1 Commits (a2e8a5ee7fecdbb2f42eeeb2343faa38cd553a15)