Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

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

  • 3 одговорa
  • 11 има овај проблем
  • 1 преглед
  • Последњи одговор послао 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.

Измењено од стране aerworker

Сви одговори (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