User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12) Gecko/20100101 Firefox/4.0b12 Build Identifier: Adobe Acrobat X (10.0.1) uses some mechanism to discover where Firefox is, then places its nppdf32.dll in a "plugins" subdirectory of the directory where Firefox was found. It does not appear to use the newer MozillaPlugins registry key mechanism. On three systems (x86 and x64, Windows 7), I have not been able to find a registry key pointing to nppdf32.dll. There is also no MOZ_PLUGIN_PATH entry created by the Acrobat installer. I suspect this is contributing to the situation in bug 636863 - if you install a beta to a new directory (as is the default), then there will not be nppdf32.dll in a "plugins" subdirectory, and therefore you will not get PDF viewing until you update/reinstall Acrobat or manually move the plugin. If someone at Adobe is watching this, or someone has a contact at Adobe, they should look into this. Reproducible: Always
This is WFM using Reader 10.1.4 and 11.0.2. I tested on a clean Windows 7 SP1 x86_64 image each time, and for both times, the MozillaPlugins registry keys were added post install. Is this still an issue?
I don't know. I haven't done anything that might have triggered this in the last two years). I do also see the MozillaPlugins registry keys now, so I suspect that Adobe did fix it...
I see... Is a WORKSFORME okay for you for now?
You might want to contact Adobe about it if there's still an issue. Cyke, this is an issue with Acrobat X, not reader. Please cancel my needinfo when you either confirm that this is fixed, or that you want it to be further looked into
(In reply to Thomas [:Tad] from comment #4) > Cyke, this is an issue with Acrobat X, not reader. Fair point...
I am seeing what seem like the proper registry entries with Acrobat 10.1.6. Haven't actually tested by installing another Firefox in a different directory. Unless anybody has any reason to suspect there still is a problem, I don't see why this bug can't be closed?
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.