Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 3 antwoorden
  • 11 hebben dit probleem
  • 8 weergaven
  • Laatste antwoord van dmitri.shchurov

aerworker
aerworker
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 in Firefox or choose another 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.

Bewerkt door aerworker op

Alle antwoorden (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.

aerworker
aerworker Vraageigenaar
more options

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

dmitri.shchurov
dmitri.shchurov
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