Class registered with a progID empty won't be accessible at the first run.

RESOLVED FIXED in M16

Status

()

Core
XPCOM
P3
minor
RESOLVED FIXED
18 years ago
10 years ago

People

(Reporter: Jean-Francois Ducarroz, Assigned: Suresh Duddi (gone))

Tracking

Trunk
All
Mac System 8.5
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
While I was working on bug 17768, I discovered that one of my class wasn't accessible the first time you run
Apprunner. The
problem was due to the fact that the progID for this class was an empty string. Now that I have set the progID to
something, It
works well.

My class was declared like this (nsMsgCompFactory.cpp):
static nsModuleComponentInfo components[] =
{
    ...
  { NS_MSGQUOTELISTENER_CID,  &nsMsgQuoteListenerConstructor, "", }
};

NS_IMPL_MODULE(nsMsgComposeModule, components)
NS_IMPL_NSGETMODULE(nsMsgComposeModule)
(Assignee)

Updated

18 years ago
Severity: major → minor
Status: NEW → ASSIGNED
Target Milestone: M16
(Assignee)

Comment 1

18 years ago
That is wierd. There are a ton of classes whose progid is oh! null.

You are giving an empty string. Can you instead make that nsnull. Empty string
ins't NULL.

I will see why empty string for progid gives such a result. Low pri though.
(Assignee)

Comment 2

18 years ago
Code fix. Now we normalize the progid passed into registration and prevent
against null or empty progid.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Updated

10 years ago
Component: XPCOM Registry → XPCOM
QA Contact: dp → xpcom
You need to log in before you can comment on or make changes to this bug.