Søg i 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

Firefox doesn't use internal PDF viewer

  • 2 svar
  • 1 har dette problem
  • 2 visninger
  • Seneste svar af Bornerdogge

more options

On certain websites, Firefox would not open PDF files in-browser using PDFJS: I get a dialog box where the only possibilities are "Cancel" and "Save the file" (not even opening the file in an external reader).

I've tried various solutions found online: - delete the "mimeTypes.rdf" in the profile folder with Firefox closed - make sure "pdfjs.disabled" is set to "false" in the "about:config" page - set the application preference to "Preview in Firefox".

Actually, even setting the preference to "Use external viewer (okular)" won't change this "save/cancel" dialog box...

It seems to be pretty random when the preview works and when not. The latest example I have is a gitlab instance (with restricted access, so I cannot share it with you unfortunately).

On certain websites, Firefox would not open PDF files in-browser using PDFJS: I get a dialog box where the only possibilities are "Cancel" and "Save the file" (not even opening the file in an external reader). I've tried various solutions found online: - delete the "mimeTypes.rdf" in the profile folder with Firefox closed - make sure "pdfjs.disabled" is set to "false" in the "about:config" page - set the application preference to "Preview in Firefox". Actually, even setting the preference to "Use external viewer (okular)" won't change this "save/cancel" dialog box... It seems to be pretty random when the preview works and when not. The latest example I have is a gitlab instance (with restricted access, so I cannot share it with you unfortunately).

Alle svar (2)

more options

Because the server is set to not open PDF inline. See https://addons.mozilla.org/fr/firefox/addon/inlinedisposition-2/

more options

Thanks, I didn't know that was something that could be configured at the server side. Anyway, even with the add-on, the problem persists...