Move DisownOpener to RenderFrameHost / RenderFrameProxyHost.

content/renderer/render_frame_impl.cc

Index: content/renderer/render_frame_impl.cc
diff --git a/content/renderer/render_frame_impl.cc b/content/renderer/render_frame_impl.cc
index ada1aa2e6ed5f21e336ea77c4edc24099f5e1af5..67925be46942becd9353ab0d1982a6749dd47b8e 100644
--- a/content/renderer/render_frame_impl.cc
+++ b/content/renderer/render_frame_impl.cc
@@ -780,6 +780,7 @@ bool RenderFrameImpl::OnMessageReceived(const IPC::Message& msg) {
 #if defined(OS_MACOSX)
     IPC_MESSAGE_HANDLER(InputMsg_CopyToFindPboard, OnCopyToFindPboard)
 #endif
+    IPC_MESSAGE_HANDLER(FrameMsg_DisownOpener, OnDisownOpener)

[nasko, 2014/08/25 15:47:14]

nit: Don't put IPC handlers after the #ifdef'd ones.

[Charlie Reis, 2014/08/25 17:10:24]

Done.

   IPC_END_MESSAGE_MAP()
 
   return handled;
@@ -1161,6 +1162,11 @@ void RenderFrameImpl::OnCopyToFindPboard() {
 }
 #endif
 
+void RenderFrameImpl::OnDisownOpener() {
+  if (frame_->opener())

[nasko, 2014/08/25 15:47:14]

Should we restrict this to main frames only? I'm not sure we have a clear
picture of what it means for a subframe to have an opener, so preserving
existing behavior might be desirable.
On the other hand, disowning an opener is "safer" operation since it will
disable operations, rather than enable, so I'm not quite sure which way is
better.

[Charlie Reis, 2014/08/25 17:10:24]

I've changed it to have a check and a TODO.  We'll need to move opener_ from
WebContents to FrameTreeNode before it makes sense to clear an opener on a
subframe.

+    frame_->setOpener(NULL);
+}
+
 void RenderFrameImpl::OnDelete() {
   frame_->executeCommand(WebString::fromUTF8("Delete"), GetFocusedElement());
 }