Fix inconsistent frame detach behavior of ContainerNode::parserRemoveChild.

Source/core/dom/Node.cpp

Index: Source/core/dom/Node.cpp
diff --git a/Source/core/dom/Node.cpp b/Source/core/dom/Node.cpp
index e2b0f14b9a4e0f3c91373fe5c57112dcce9ad919..19513db6ff35c8f9d0608753f4b3f68134b91017 100644
--- a/Source/core/dom/Node.cpp
+++ b/Source/core/dom/Node.cpp
@@ -2258,17 +2258,6 @@ void Node::decrementConnectedSubframeCount(unsigned amount)
     rareData()->decrementConnectedSubframeCount(amount);
 }
 
-void Node::updateAncestorConnectedSubframeCountForRemoval() const
-{
-    unsigned count = connectedSubframeCount();
-
-    if (!count)
-        return;
-
-    for (Node* node = parentOrShadowHostNode(); node; node = node->parentOrShadowHostNode())
-        node->decrementConnectedSubframeCount(count);

[Yuta Kitamura, 2015/02/23 07:54:41]

Simply removing this function makes the "connectedSubframeCount"
number inconsistent, no? ChildFrameDisconnector does not seem
to be doing this.

[kouhei (in TOK), 2015/02/23 11:51:29]

HTMLFrameOwnerElement::clearContentFrame does this.

-}
-
 void Node::updateAncestorConnectedSubframeCountForInsertion() const
 {
     unsigned count = connectedSubframeCount();