Hold a strong ref to the node we plan to remove, since we want to use it after

removing it from the tree.  Bug 221494, r+sr=jst


git-svn-id: svn://10.0.0.236/trunk@148869 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
bzbarsky%mit.edu
2003-11-05 17:54:46 +00:00
parent 604427b585
commit a8b6d7c39d

View File

@@ -1422,7 +1422,7 @@ nsXULContentBuilder::RemoveGeneratedContent(nsIContent* aElement)
PRUint32 i = element->GetChildCount();
while (i-- > 0) {
nsIContent *child = element->GetChildAt(i);
nsCOMPtr<nsIContent> child = element->GetChildAt(i);
// Optimize for the <template> element, because we *know*
// it won't have any generated content: there's no reason
@@ -1446,7 +1446,6 @@ nsXULContentBuilder::RemoveGeneratedContent(nsIContent* aElement)
// If we get here, it's "generated". Bye bye!
element->RemoveChildAt(i, PR_TRUE);
child->SetDocument(nsnull, PR_TRUE, PR_TRUE);
// Remove element from the conflict set.
// XXXwaterson should this be moved into NoteGeneratedSubtreeRemoved?