Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

PDF.js removing PDF security

  • 1 பதிலளி
  • 1 இந்த பிரச்சனை உள்ளது
  • 15 views
  • Last reply by guigs

I am facing similar problems as discussed in the below mentioned forum post

https://support.mozilla.org/en-US/questions/1014746

PDF.js is not considering the enabled PDF security. The functionality what i want to achieve is to control the print to file option using tools like CutePDF. If a user tries to print the PDF to a file and PDF is created by setting encryption is opened in Adobe reader, the saved PDF will be blank. But this is not happening in PDF.js and it is saving the content of the PDF. Can this be handled in PDF.js?

I am facing similar problems as discussed in the below mentioned forum post https://support.mozilla.org/en-US/questions/1014746 PDF.js is not considering the enabled PDF security. The functionality what i want to achieve is to control the print to file option using tools like CutePDF. If a user tries to print the PDF to a file and PDF is created by setting encryption is opened in Adobe reader, the saved PDF will be blank. But this is not happening in PDF.js and it is saving the content of the PDF. Can this be handled in PDF.js?

All Replies (1)

I am hearing you say that you do not want it to print the content and you want the security to create the page blank. It looks like it should handle security according to the bug mentioned. https://bugzilla.mozilla.org/show_bug.cgi?id=792816#c12