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.

Etsi tuesta

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.

Lue lisää

Is there way to check in javascript code if built in PDF.js viewer is disabled

  • 3 vastausta
  • 11 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja dmitri.shchurov

more options

To restore functionality of my site I want to ask user to disable built in PDF.js viewer. To determine if Adobe acrobat reader plug-in is enabled i check navigator.mimeTypes["application/pdf"].enabledPlugin property. But this plug-in seems to be enabled independently from the setting described in View PDF files using Firefox’s built-in viewer article. So is there a way to determine in javascript code if 'Preview in Firefox' or 'Use Adobe Acrobat (in Firefox)' values are set.

To restore functionality of my site I want to ask user to disable built in PDF.js viewer. To determine if Adobe acrobat reader plug-in is enabled i check navigator.mimeTypes["application/pdf"].enabledPlugin property. But this plug-in seems to be enabled independently from the setting described in [[View PDF files in Firefox without downloading them]] article. So is there a way to determine in javascript code if 'Preview in Firefox' or 'Use Adobe Acrobat (in Firefox)' values are set.

Muokattu , muokkaaja aerworker

Kaikki vastaukset (3)

more options

A possibility might be to check the navigator.plugins array and search for the Adobe Reader plugin.
The PDF Viewer (pdfjs) doesn't seem to show there.

more options

I've filed to determine difference by the window.navigator.plugins property too.

more options

cor-el, the more your answers I found the more i'm confident you do not think about the problem described. It's sad, that mozila pay more attention on new mobile os, than on old user problems. Chrome will bite you for sure