Streamline frame detach

Source/web/RemoteFrameClient.cpp

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "config.h"
 #include "web/RemoteFrameClient.h"
 
 #include "platform/weborigin/SecurityOrigin.h"
 #include "web/WebLocalFrameImpl.h"
 #include "web/WebRemoteFrameImpl.h"
 
 namespace blink {
 
 RemoteFrameClient::RemoteFrameClient(WebRemoteFrameImpl* webFrame)
     : m_webFrame(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());
 }
 
 void RemoteFrameClient::setOpener(Frame*)
 {
     // FIXME: Implement.
 }
 
@@ skipping 29 matching lines @@
 
 bool RemoteFrameClient::willCheckAndDispatchMessageEvent(
     SecurityOrigin* target, MessageEvent* event, LocalFrame* sourceFrame) const
 {
     if (m_webFrame->client())
         m_webFrame->client()->postMessageEvent(WebLocalFrameImpl::fromFrame(sourceFrame), m_webFrame, WebSecurityOrigin(target), WebDOMMessageEvent(event));
     return true;
 }
 
 } // namespace blink