|
|
Rank: Advanced Member
Groups: Member
Joined: 1/31/2015
Posts: 70
|
Hello,
Just a heads up for a problem that we are trying to reproduce.
A few of our clients cannot print through the embedded pdf plugin. They click the print button, choose the default printer and then click 'print'. The result is that the command is "lost" somewhere in space. It never gets communicated to the printer. Saving the file and then printing from windows (through any pdf viewer) is the only way for them to print.
We have not been able yet to collect the conditions which 'abort' the printing process through the plugin.
I will return with more findings
Kind regards,
Jim
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, Please try to set this property to true and see if it works for you: http://www.essentialobjects.com/doc/eo.webbrowser.runtime.disablebuiltinplugins.aspxThis will disable the built-in PDF plug-in and loads Adobe's plug-in (if Adobe Reader is installed on the customer's machine) instead. You can then try to print it there and see if it works. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/31/2015
Posts: 70
|
Hello,
Thanks for replying.
Your suggestion is valid but has a couple of tricky bits:
1) we don't have an exact reproducible scenario yet, so even if we switch to another plugin (adobe's) we won't know until weeks have passed and customers have stopped calling about printing
2) customers use a variety of pdf readers (adobe's, sumatra, foxit to name a few). Informing them that they have to install an additional piece of software is also going to take time
I think that the best bet for us would be that we succeeded in reproducing the issue so that you can have a closer look.
Regards,
Jim
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
I agree with you that the best is if we can reproduce the problem. However given the fact that it actually works on most computers, so my gut guess is that this might be an issue on Chrome's side. In that case we will not be able to fix it since Chrome is simply too huge a project for us to fix things. It will became unmanageable for us if we were to do that. For that reason, if the problem is in Chrome's code, we usually wait until we sync with Chrome's code again.
On a side note, we did have user reporting Foxit PDF printer sometimes cause problem with Chrome printing. So you might want to check if that is the case.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/31/2015
Posts: 70
|
Yes, I agree. If it's at Chrome's end, we will follow your approach (switch to adobe's plugin).
I see v2.53.
Is "Fixed WebView.AfterPrint not fired issue" relevant?
Cheers,
Jim
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
No. This has nothing to do with your case. That fix was the printing works fine, but AfterPrint event was not fired.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/31/2015
Posts: 70
|
Ok ok :)
We're putting this issue on hold until we have more feedback from clients.
Thanks for the quick reply
jim
|
|