X
Tap here to go to the mobile version of the site.

Support Forum

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

Posted

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.

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.

Modified by aerworker

Additional System Details

Application

  • User Agent: Opera/9.80 (Windows NT 6.1; WOW64; U; en) Presto/2.10.229 Version/11.62

More Information

cor-el
  • Top 10 Contributor
  • Moderator
12528 solutions 115512 answers

Helpful Reply

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.

A possibility might be to check the navigator.plugins array and search for the Adobe Reader plugin.<br /> The PDF Viewer (pdfjs) doesn't seem to show there. *http://developer.mozilla.org/en/DOM/window.navigator.plugins

Helpful Reply

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

I've filed to determine difference by the window.navigator.plugins property too.
dmitri.shchurov 0 solutions 2 answers

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

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