nsPluginManager doesn't appear to have a progID.
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)?
Reassigning to av.
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.
Not a Netscape 6 RTM blocker. FUTURE. This bug has been marked Future because the Netscape engineer it is assigned to is overburdened.
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?
this is a wontfix, no one should be using this, it is deprecated