Bug 401276 - Fix comment that claims that Range.ExtractContents should merge resulting adjacent nodes, r=smaug
--- a/content/base/src/nsRange.cpp
+++ b/content/base/src/nsRange.cpp
@@ -1445,28 +1445,16 @@ nsresult nsRange::CutContents(nsIDOMDocu
tmpNode = newCloneAncestor;
tmpNode->GetParentNode(getter_AddRefs(newCloneAncestor));
NS_ENSURE_STATE(newCloneAncestor);
}
commonCloneAncestor = newCloneAncestor;
}
}
- // XXX_kin: At this point we should be checking for the case
- // XXX_kin: where we have 2 adjacent text nodes left, each
- // XXX_kin: containing one of the range end points. The spec
- // XXX_kin: says the 2 nodes should be merged in that case,
- // XXX_kin: and to use Normalize() to do the merging, but
- // XXX_kin: calling Normalize() on the common parent to accomplish
- // XXX_kin: this might also normalize nodes that are outside the
- // XXX_kin: range but under the common parent. Need to verify
- // XXX_kin: with the range commitee members that this was the
- // XXX_kin: desired behavior. For now we don't merge anything!
- // XXX ajvincent Filed as https://bugzilla.mozilla.org/show_bug.cgi?id=401276
-
rv = CollapseRangeAfterDelete(this);
if (NS_SUCCEEDED(rv) && aFragment) {
NS_ADDREF(*aFragment = retval);
}
return rv;
}
NS_IMETHODIMP