Closed Bug 12258 Opened 26 years ago Closed 25 years ago

[Tree]treechildren.removeChild(treeitem) does not remove the children of the treeitem

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Platform:
PowerPC
Mac System 8.6
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: hangas, Assigned: hyatt)

References

Details

When trying to delete rows from a tree I discovered that removing the treeitem node from the treechildren node did not properly remove the children of the treeitem node. In fact the children of that node appeared in the window below the tree. To work-around I recursively remove all the children from the treeitem before removing it and things are fine. Waterson suggested that this might be a bug in the tree code.
My guess is that the ContentRemoved handler is not quite right.
Status: NEW → ASSIGNED
Target Milestone: M10
Please attach your tree XUL.
Blocks: 12716
Target Milestone: M10 → M14
moving to m14
Blocks: 15008
Assignee: hyatt → hangas
Status: ASSIGNED → NEW
reassigning to hangas to get requested attachment
Target Milestone: M14
Status: NEW → ASSIGNED
Target Milestone: M12
Summary: treechildren.removeChild(treeitem) does not remove the children of the treeitem → [Tree]treechildren.removeChild(treeitem) does not remove the children of the treeitem
Marking [Tree]
Assignee: hangas → alecf
Status: ASSIGNED → NEW
Target Milestone: M12
The problem seems to be just the html elements inside of the tree. The xul elements are removed, but the html elements like html:input and html:select are not being removed. They just end up displayed in the window outside of the tree after the removeChild(). Sending to alecf per his suggestion.
Status: NEW → ASSIGNED
Target Milestone: M15
my theory is this is in nsXULElement somewhere. It could be another one of these if (mDocument...) bugs that putterman found last week. However, it can wait until after beta1, since paul has a workaround.
giving me rest of phillips open qa contact bugs, sorry for spam
Assignee: alecf → hyatt
Status: ASSIGNED → NEW
reassigning tree bugs back to hyatt. this bug may even already be fixed. It would be great if the QA contact here could verify this bug is still broken.
Status: NEW → ASSIGNED
Target Milestone: M15 → M16
This is just a view destruction problem. I believe this has been fixed by the switchover to GFX widgets.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
please ignore, massive spam giving jrgm@netscape.com backlog of XPToolkits resolved fixed bugs to verify
QA Contact: paulmac → jrgm
Verified Fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.