You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug On Ipad the second time that print action is executed device ask for the user about if allow or not the print process, because it was blocked by the browser. When user press allow, the print information doesn't exist. I have already created a PR ti fix it https://github.com/jasonday/printThis/pull/181/files.
To Reproduce
Steps to reproduce the behavior:
Execute print function in an Ipad mini more than one time.
Additional context
In the library is as default remove iframe exactly after one second the print function has been executed. It should be until called on afterprint function, in the library
The text was updated successfully, but these errors were encountered:
This is the same issue as #137
Users only experience the issue if they cancel the first print. We do not have a workaround at this time.
The native afterprint event is not supported consistently across all browsers, so the "after print" callback is fired after the printDelay, before the one second delay for the iframe removal.
FYI this is happening also on FF 69.0.3 and Chrome 77.0.3865.120 both on Windows 10 and yes it is only when print is cancelled. Would appreciate a nudge here perhaps once a fix has been made? Thank you!
Describe the bug On Ipad the second time that print action is executed device ask for the user about if allow or not the print process, because it was blocked by the browser. When user press allow, the print information doesn't exist. I have already created a PR ti fix it https://github.com/jasonday/printThis/pull/181/files.
To Reproduce
Steps to reproduce the behavior:
Additional context
In the library is as default remove iframe exactly after one second the print function has been executed. It should be until called on afterprint function, in the library
The text was updated successfully, but these errors were encountered: