daphnesmit / prntr Goto Github PK

Hello I want to add this script to my website like Printer.js

prntr.cjs.js:3 Uncaught ReferenceError: process is not defined
    at prntr.cjs.js:3:5
(anonymous) @ prntr.cjs.js:3
prntr.esm.js:1 Uncaught SyntaxError: Cannot use import statement outside a module

Help me :(

Hi!

The latest version doesn't trigger onPrintDialogClose in Firefox anymore.

I tried downgrading to version 2.0.1 and that solved the problem, so the regression is in one of the later versions since then.

I'm on Windows 11.

Looks like those navigators need to be checked for, at least for SSR:

Chrome version: 97.0.4692.99
Windows version: 21H2 (19044.1466)

As per the title, the iframe is remaining in the DOM after closing the chrome print dialog. It is only removed if I unfocus the window and refocus it.

The impact of this is bigger than you would expect, as in my Vue-Router app using browser nav to go back then forward again will reopen the print dialog as soon as the component for that route loads.

Can you add possibility to add footer? Same as addHeader. Thank you.

Hi !

Is there any possibility to get a cancel/print event ?
Maybe within the onPrintDialogClose property ?

I need to save the information that some files have been printed, i can't find any solution.

Thank your for your great work !

Regards

When printing a pdf using Safari on an iPad it only prints the first page.

Any idea how to resolve this?

Hi

There seems to be some code in your library that wants to use the focus event for Chrome and Firefox to trigger the onPrintDialogClose callback. The problem is that Browser$1.isChrome() returns false for me in Chrome 97.0.4692.99 (Win 11), causing it to keep listening for mouseover.

This prevents onPrintDialogClose from getting called.

If I set a breakpoint on line 103 in your code and overwrite the event variable with the value focus using the console, then the callback gets triggered without any need to move the mouse around.

Maybe there is a better way you can test which browser is being used? Alternatively accept a config option that lets the application tell prntr which browser is running (which in my case would be easy since I'm using the bowser library). Since this is a TS library, a discriminated union of 'Chrome' | 'Edge' | 'Firefox' | ... would make for a neat API design that prevents mistakes.