This content has been marked as final. Show 10 replies
Can users disable this prompt by either turning off a security setting or adding my site to a list of trusted sites?
Silent/automatic printing is an important feature of my application, and this really thwarts that. I'd like for my users to have the ability to allow PDFs served from my domain name to print automatically without prompting.
Is there a way a user can disable this notification?
There is no indication of this. Since it is a security feature, simply
disabling it would leave the user wide open to security breaches. The
only secure solution would be a directed one (e.g. allow PDF files
with THIS digital signature to print), which doesn't seem to exist.
And I love the idea that somehow presenting a message for an average user to divine whether it's safe or not is going to actually make things more secure. They have no clue.
So, it's now just yet another click that will annoy them. Too bad Adobe couldn't resolve the underlying issue instead of punting.
Oops.. my application can't support slient print any more ...
I like Adam's idea, allow the user to add to trusted sites and disable the notification. I understand the vulnerability, however our users want us to be able to print the docs we serve without any user intervention. Will Adobe consider this?
This additional security causes numerous problems for us as well. I create interactive forms which are filled out both internally as well as by web users (via download). After the form is filled out, I have "Save" button, which actually does not save, but prints to PDF, closes the interactive version, and opens the new flat file -- thereby making the form non-interactive and suitable for upload into our system. We need non-interactive forms because our system does not support ANY interactive forms (government app). With the new security, if the user says NO to printing, the document closes and all input is lost! Not so good.
Please advise!! Thank you!
I agree please allow us to turn this feature off.
I have found a work around to this problem not nice but it works.