Closed Bug 78224 Opened 24 years ago Closed 24 years ago

nsGlobalWindow.cpp: NavigatorImpl::JavaEnabled should ask OJI, not Plugins.

Categories

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

defect
Not set
major

Tracking

()

VERIFIED FIXED

People

(Reporter: edburns, Assigned: edburns)

Details

(Whiteboard: [oji_working])

Attachments

(1 file)

The method stated in the Summary asks the plugin sub-system if java is enabled. This method fails when it happens that java isn't implemented via a plugin, but rather as an XPCOM component, as is the case in future implementations of java. In any case, it is more correct to ask the OJI service about the enabled status of Java than it is to ask the plugins. I'm attaching a diff. I'd like to get this into the trunk.
a
Status: NEW → ASSIGNED
Whiteboard: [oji_working]
Not sure why joki, dr, and hyatt are cc'd, but not jst. Adding XPCOM buddies. Are you sure you want a CID (SID, warren wouuld say; GUID that identifies a particular implementation of a "class" or "service") rather than a contractid? /be
Thanks Brendan, I'll use the contract ID. Given that, can you give sr=brendan?
How about jst, the module owner, gives an r= first? Let my sr= depend on that, you don't need to ask me again. /be
r/sr=jst
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updating QA contact to Shivakiran Tummala.
QA Contact: desale → stummala
according to the developers comments the fix was checked in . Marking Verified
Status: RESOLVED → VERIFIED
Component: DOM: Core → DOM: Core & HTML
QA Contact: stummala → general
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: