Avatar for Username

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Learn More

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 3 respostas
  • 11 têm este problema
  • 1 visualização
  • Última resposta de 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.

Alterado por aerworker em

Todas as respostas (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 Autor da pergunta
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