Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

PDF Security Settings are being ignored by Firefox

  • 3 Mbohovái
  • 0 oguereko ko apañuãi
  • 4 Hecha
  • Mbohovái ipaháva TyDraniu

Why has Mozilla decided to COMPLETELY IGNORE security settings applied to PDF documents? I have a number of PDFs secured so as to prevent the ability to print or copy text. When opened with Firefox, all of these settings are ignored.

Why has Mozilla decided to COMPLETELY IGNORE security settings applied to PDF documents? I have a number of PDFs secured so as to prevent the ability to print or copy text. When opened with Firefox, all of these settings are ignored.

Opaite Mbohovái (3)

The current state of things, given the existing code:

  • None of these document permissions are enabled/enforced by default in the PDF.js viewer, which thus includes the built-in Firefox PDF Viewer.
  • When the pdfjs.enablePermissions preference is set (in about:config), currently only copying is disabled and the text-selection cursor is then replaced with the "not-allowed" cursor (to indicate that text-selection/copying is prevented); see also PR #11789 and bug 792816 .
  • The rest of the document permissions are currently not implemented.

That doesn't answer my question. Why has Mozilla decided that they don't need to abide by restrictions set by a document's creator?

Do you think everything must have a reason? Perhaps there's only "why should we implement it anyway".

I already linked the full discussion about it. If you need it, just flip the pref.

Eporandumína

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.