Streamline frame detach

Source/web/RemoteFrameClient.cpp

Index: Source/web/RemoteFrameClient.cpp
diff --git a/Source/web/RemoteFrameClient.cpp b/Source/web/RemoteFrameClient.cpp
index ff9d6a1fee986d103d4348c9e8cc5878709b5384..f745290d954ac775840e7c990684355e15abb142 100644
--- a/Source/web/RemoteFrameClient.cpp
+++ b/Source/web/RemoteFrameClient.cpp
@@ -16,6 +16,11 @@ RemoteFrameClient::RemoteFrameClient(WebRemoteFrameImpl* webFrame)
 {
 }
 
+void RemoteFrameClient::detached()
+{
+    // FIXME: Implement.

[dcheng, 2014/09/25 23:35:44]

What do you have in mind here? Or is this just so we can pull the detached()
call up into Frame?

[Nate Chapin, 2014/09/25 23:57:51]

Mostly so we can pull the detached() call up into Frame.

But also, I figured the odds are decent that RemoteFrames will need to do some
work when detach occurs eventually.

+}
+
 Frame* RemoteFrameClient::opener() const
 {
     return toCoreFrame(m_webFrame->opener());