Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

PDF.js removing PDF security

  • 1 svar
  • 1 har detta problem
  • 15 visningar
  • Senaste svar av guigs

tinto.chacko1
tinto.chacko1
more options

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?

Alla svar (1)

guigs
guigs
more options

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