Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

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.

Bewurke troch aerworker op

Alle antwurden (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