Closed Bug 18848 Opened 21 years ago Closed 18 years ago

PICS needs some serious XPCOM work

Categories

(SeaMonkey :: General, enhancement, P1)

x86
Windows NT
enhancement

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.
Priority: P3 → P1
Severity: normal → enhancement
Setting severity to enahancement. This aint shipping for this release. Plus we
are pulling pics off opensource.
Status: NEW → ASSIGNED
Target Milestone: M16
PICS is moving out of opensource for now.
Target Milestone: M16 → M20
changing qa contact on selected bugs from paulmac to elig@netscape.com
QA Contact: paulmac → elig
Target Milestone: M20 → Future
helpwanted
Assignee: neeti → nobody
Status: ASSIGNED → NEW
Keywords: helpwanted
QA Contact: elig → neeti
What is the status of PICS?
Given that extensions/pics/ no longer exists, shouldn't this bug be resolved
INVALID?
I think that is correct. INVALID.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Component: PICS → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.