Closed Bug 512214 Opened 15 years ago Closed 15 years ago

navigator.javaEnabled() produces bogus results with the new Sun plugin

Categories

(Core :: DOM: Core & HTML, defect, P2)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows XP
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
status1.9.2 --- beta1-fixed
status1.9.1 --- wanted

People

(Reporter: neil, Assigned: jaas)

References

Details

(Keywords: regression)

When using 1.9.1 with the OJI plugin, navigator.javaEnabled() returns true if the plugin is installed and enabled and false if it is not. When using 1.9.1 with the NPAPI plugin, navigator.javaEnabled() returns true if the plugin is installed and enabled but not started. After OJI tries and fails to start Java, navigator.javaEnabled() returns false. When using 1.9.2 with the NPAPI plugin, navigator.javaEnabled() does not detect whether the plugin is installed. Instead, it only returns the java preference.
Flags: blocking1.9.2?
This is probably fixed by bug 506985, may need a different patch for branches.
Not blocking a 1.9.1 release, but a fix would be nice once we figure out how to fix it on the trunk/1.9.2 (where it may be a blocker).
blocking1.9.1: ? → ---
status1.9.1: --- → wanted
Josh, can you verify whether bug 506985 actually fixed this?
Assignee: nobody → joshmoz
Flags: blocking1.9.2? → blocking1.9.2+
Priority: -- → P2
Looks fixed to me, tested on Windows Vista with Firefox 3.6 nightly.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Depends on: 506985
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.