If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

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

RESOLVED FIXED

Status

()

Core
DOM
P2
normal
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: neil@parkwaycc.co.uk, Assigned: Josh Aas)

Tracking

({regression})

Trunk
x86
Windows XP
regression
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.9.2 +

Firefox Tracking Flags

(status1.9.2 beta1-fixed, status1.9.1 wanted)

Details

(Reporter)

Description

8 years ago
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?
(Assignee)

Comment 1

8 years ago
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

Comment 3

8 years ago
Josh, can you verify whether bug 506985 actually fixed this?
Assignee: nobody → joshmoz
Flags: blocking1.9.2? → blocking1.9.2+
Priority: -- → P2
(Assignee)

Comment 4

8 years ago
Looks fixed to me, tested on Windows Vista with Firefox 3.6 nightly.
(Assignee)

Updated

8 years ago
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED

Updated

8 years ago
status1.9.2: --- → beta1-fixed
Depends on: 506985
You need to log in before you can comment on or make changes to this bug.