Closed
Bug 18848
Opened 26 years ago
Closed 24 years ago
PICS needs some serious XPCOM work
Categories
(SeaMonkey :: General, enhancement, P1)
Tracking
(Not tracked)
RESOLVED
INVALID
Future
People
(Reporter: travis, Unassigned)
References
()
Details
(Keywords: helpwanted)
I was needing to change some usagages of interfaces today and that brought me
into the PICS code. There is a lot of work that needs to be done in here with
regard to making it XPCOM compliant. This code is virtually without an
refcounting at all. I added a bit, but the owner needs to look through the
code, determine the memory ownership model and apply it through out. At this
point all interfaces pointers should switch to nsCOMPtr. If there are any
questions on what exactly needs to be done in this file, come see me.
Updated•26 years ago
|
Severity: normal → enhancement
Comment 1•26 years ago
|
||
Setting severity to enahancement. This aint shipping for this release. Plus we
are pulling pics off opensource.
Comment 3•26 years ago
|
||
changing qa contact on selected bugs from paulmac to elig@netscape.com
QA Contact: paulmac → elig
helpwanted
Updated•25 years ago
|
QA Contact: elig → neeti
Comment 5•24 years ago
|
||
What is the status of PICS?
Comment 6•24 years ago
|
||
Given that extensions/pics/ no longer exists, shouldn't this bug be resolved
INVALID?
Comment 7•24 years ago
|
||
I think that is correct. INVALID.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•23 years ago
|
Component: PICS → Browser-General
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•