fix ownership model in nsXULDocument

RESOLVED FIXED in M7

Status

()

Core
XUL
P3
normal
RESOLVED FIXED
20 years ago
10 years ago

People

(Reporter: Mike Pinkerton (not reading bugmail), Assigned: Mike Pinkerton (not reading bugmail))

Tracking

Trunk
All
Mac System 8.5
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

20 years ago
scc and i got about 1/2 way through fixing the ownership model in nsXULDocument
when fixing the webShell leakage. Someone needs to go back and finish the job.

waterson should probably own this down the road, but scc is the best candidate to
finish in the short term.

Updated

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

Comment 1

19 years ago
I definitely want to finish this for M7
(Assignee)

Updated

19 years ago
Assignee: scc → pinkerton
Status: ASSIGNED → NEW
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 2

19 years ago
taking over for scc so it gets done.
(Assignee)

Comment 3

19 years ago
accepting bug.

Comment 4

19 years ago
Yo Pink, could you tell me what's wrong? I replaced owning pointers with
nsCOMPtr's a while ago...
(Assignee)

Comment 5

19 years ago
What's wrong is that you're just too damn good for the rest of us. If you've done
it already, then there's no need for this bug anymore. ;)
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 6

19 years ago
Looks like waterson is 5 steps ahead of us, as usual. Marking fixed.

Updated

19 years ago
QA Contact: gerardok → ckritzer

Comment 7

19 years ago
Changing QA Contact to ckritzer@netscape.com.

Comment 8

19 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Comment 9

19 years ago
Massive QA Contact update.
QA Contact: ckritzer → jrgm

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.