nsPluginManager missing contractID

VERIFIED WONTFIX

Status

()

Core
Plug-ins
P3
normal
VERIFIED WONTFIX
18 years ago
16 years ago

People

(Reporter: Braden, Assigned: av (gone))

Tracking

({arch})

Trunk
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
nsPluginManager doesn't appear to have a progID.

Comment 1

18 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)?

Comment 2

17 years ago
Reassigning to av.
Assignee: warren → av
(Reporter)

Comment 3

17 years ago
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
(Reporter)

Updated

17 years ago
Keywords: arch
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
(Reporter)

Comment 5

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

16 years ago
this is a wontfix, no one should be using this, it is deprecated
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 7

16 years ago
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.