JDK-6682408 : DT plugin for Firefox is disabled when new plug-in is enabled
- Type: Bug
- Component: install
- Sub-Component: install
- Affected Version: 6u10
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: windows
- CPU: generic
- Submitted: 2008-03-31
- Updated: 2010-09-17
- Resolved: 2008-04-29
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 | JDK 7 |
|---|---|
6u10 b23Fixed  |
7Fixed |
Related Reports
|
Relates :
|
Description
During the fix for 6635585 (Modify plug-in switching mechanism to better support Firefox), we moved the new plug-in's Firefox DLL into bin/new_plugin and changed Firefox 3 to conditionally search that directory for plugins instead of the JRE's bin directory, if the registry key indicating to use the new Java Plug-In is set. Unfortunately, this broke the finding of the DT plugin for Firefox (npdeploytk.dll) because this is only present in the "bin" directory. To fix this, we need to modify the installer to make a copy of npdeploytk.dll from the bin/ directory to the bin/new_plugin/ directory, and to clean up this copy during uninstallation.
Comments
|