Bug 401276 - Fix comment that claims that Range.ExtractContents should merge resulting adjacent nodes, r=smaug
authorAlex Vincent <ajvincent@gmail.com>
Wed, 23 Mar 2011 15:13:40 -0400
changeset 63558 63f173e21fd1ee205be00134bb1a9b607bcb3de5
parent 63557 7e1308fc3b70b9ac4612f453d49effea67d22c08
child 63559 e92ddaea90ae2985b63483360f1e9a07f7cabed9
push idunknown
push userunknown
push dateunknown
reviewerssmaug
bugs401276
milestone2.2a1pre
Bug 401276 - Fix comment that claims that Range.ExtractContents should merge resulting adjacent nodes, r=smaug
content/base/src/nsRange.cpp
--- 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