PICS needs some serious XPCOM work

RESOLVED INVALID

Status

P1
enhancement
RESOLVED INVALID
20 years ago
14 years ago

People

(Reporter: travis, Unassigned)

Tracking

({helpwanted})

Trunk
Future
x86
Windows NT
helpwanted

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

20 years ago
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.
(Reporter)

Updated

20 years ago
Priority: P3 → P1

Updated

20 years ago
Severity: normal → enhancement
Setting severity to enahancement. This aint shipping for this release. Plus we
are pulling pics off opensource.

Updated

20 years ago
Status: NEW → ASSIGNED
Target Milestone: M16

Comment 2

20 years ago
PICS is moving out of opensource for now.

Updated

19 years ago
Target Milestone: M16 → M20

Comment 3

19 years ago
changing qa contact on selected bugs from paulmac to elig@netscape.com
QA Contact: paulmac → elig

Updated

19 years ago
Target Milestone: M20 → Future

Comment 4

19 years ago
helpwanted
Assignee: neeti → nobody
Status: ASSIGNED → NEW
Keywords: helpwanted

Updated

19 years ago
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
Last Resolved: 17 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.