Bug 401276 - Fix comment that claims that Range.ExtractContents should merge resulting adjacent nodes, r=smaug

This commit is contained in:
Alex Vincent 2011-03-23 15:13:40 -04:00
parent 3623fe7d48
commit 74af4ff8ab

View File

@ -1450,18 +1450,6 @@ nsresult nsRange::CutContents(nsIDOMDocumentFragment** aFragment)
} }
} }
// 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); rv = CollapseRangeAfterDelete(this);
if (NS_SUCCEEDED(rv) && aFragment) { if (NS_SUCCEEDED(rv) && aFragment) {
NS_ADDREF(*aFragment = retval); NS_ADDREF(*aFragment = retval);