Make removeChild faster with active ranges

third_party/WebKit/Source/core/dom/ContainerNode.cpp

Index: third_party/WebKit/Source/core/dom/ContainerNode.cpp
diff --git a/third_party/WebKit/Source/core/dom/ContainerNode.cpp b/third_party/WebKit/Source/core/dom/ContainerNode.cpp
index 2f7a45335c8c3922b46955a5755e994329ba536d..c84626d91ccac8d02a52fa3d09eb7c94405555da 100644
--- a/third_party/WebKit/Source/core/dom/ContainerNode.cpp
+++ b/third_party/WebKit/Source/core/dom/ContainerNode.cpp
@@ -772,19 +772,9 @@ void ContainerNode::detach(const AttachContext& context)
     Node::detach(context);
 }
 
-bool ContainerNode::shouldNotUpdateRangesAfterChildrenChanged(const ChildrenChange& change)
-{
-    return change.byParser
-        || change.type == TextChanged
-        || change.type == ElementInserted
-        || change.type == NonElementInserted;
-}
-
 void ContainerNode::childrenChanged(const ChildrenChange& change)
 {
     document().incDOMTreeVersion();
-    if (!shouldNotUpdateRangesAfterChildrenChanged(change))
-        document().updateRangesAfterChildrenChanged(this);
     invalidateNodeListCachesInAncestors();
     if (change.isChildInsertion() && !childNeedsStyleRecalc()) {
         setChildNeedsStyleRecalc();