Closed
Bug 316558
Opened 19 years ago
Closed 19 years ago
Stop supporting a few old nsIComponentManagerObsolete methods
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla1.9alpha1
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
Attachments
(1 file)
5.39 KB,
patch
|
darin.moz
:
review+
|
Details | Diff | Splinter Review |
There are a few old nsIComponentManagerObsolete methods that I would like to stop implementing, so that I can do this nsIComponentLoader->nsIModuleLoader thing more easily: unregisterComponent() unregisterComponentSpec() These functions are not used anywhere in our code except a couple of obsolete tests.
Assignee | ||
Comment 1•19 years ago
|
||
Comment 2•19 years ago
|
||
nsIComponentManagerObsolete is used with plugins, no? are you sure that there aren't any plugins in use that need this?
Assignee | ||
Comment 3•19 years ago
|
||
Pretty sure, yes... plugins do not typically register or unregister any components by location, if anything they register factories/services at runtime only.
Comment 4•19 years ago
|
||
Yeah, that would be my *guess* as well. So, you want to just break it and see what happens then?
Assignee | ||
Comment 5•19 years ago
|
||
Yes. It's likely that the moduleloader patch would change the way it works anyway, so I'm trying to reduce risk by splitting that up into small digestible and testable pieces.
Comment 6•19 years ago
|
||
Comment on attachment 203131 [details] [diff] [review] Stop implementing obsolete methods, rev. 1 Well, always good to remove dead code ;-) r=darin *crossing fingers*
Attachment #203131 -
Flags: review?(darin) → review+
Assignee | ||
Comment 7•19 years ago
|
||
Fixed on trunk.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•