akira/pdfjs-dist - pdfjs-dist - Gitea: Git with a cup of tea

Tree: 24a7a58da7

Author	SHA1	Message	Date
Yury Delendik	24a7a58da7	Moves mozPrintCallback specific code to firefox_printservice.js	9 years ago
Rob Wu	76d29759c5	Avoid window.print in a microtask	9 years ago
Yury Delendik	006e8fb59d	Introduces UMD headers to the web/ folder.	9 years ago
Manas	a2ba1b8189	Uses editorconfig to maintain consistent coding styles Removes the following as they unnecessary /* -- Mode: Java; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -- / / vim: set shiftwidth=2 tabstop=2 autoindent cindent expandtab: */	10 years ago
Rob Wu	f4ba0e342e	Check availability of canvas & PDF before printing	10 years ago
Rob Wu	9df998914d	Print shortcut: Ctrl + (Shift +) P only The previous version interfered with the full screen shortcut (Ctrl + Alt + P). The new version only intercepts Cmd/Ctrl + P (all browsers). And Ctrl + Shift + P in Chrome / Opera (Presto and Chromium), because these browsers also associate a Print operation with the shortcut.	11 years ago
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