Closed
Bug 44967
Opened 24 years ago
Closed 22 years ago
nsPluginManager missing contractID
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
VERIFIED
WONTFIX
Future
People
(Reporter: braden, Assigned: serhunt)
Details
(Keywords: arch)
nsPluginManager doesn't appear to have a progID.
Comment 1•24 years ago
|
||
Is its CID frozen? I'm doing a CreateInstance using the current CID. Will it change before/after netscape 6 is released? Even if it gets a progID, does it matter (will my code break)?
rayw: CC'ing you on this one in light of the progID -> contractID transition. sean: I don't see any reason the CID should change; code that uses the CID should continue to work. Changing summary to reflect newspeak.
Summary: nsPluginManager missing progID → nsPluginManager missing contractID
Comment 4•24 years ago
|
||
Not a Netscape 6 RTM blocker. FUTURE. This bug has been marked Future because the Netscape engineer it is assigned to is overburdened.
Target Milestone: --- → Future
Adding mozilla1.0 to put this on the radar, but I suspect it should be WONTFIX. Isn't nsPluginManager part of the deprecated XPCOM plugin API?
Keywords: mozilla1.0
Comment 6•22 years ago
|
||
this is a wontfix, no one should be using this, it is deprecated
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•