Notifying the Out of Process Renderer about Visibility Change of a Remote Frame

content/browser/frame_host/cross_process_frame_connector.cc

Index: content/browser/frame_host/cross_process_frame_connector.cc
diff --git a/content/browser/frame_host/cross_process_frame_connector.cc b/content/browser/frame_host/cross_process_frame_connector.cc
index aae77095658467e30fe8227f56b4eff7cbea9a06..1a92ca4130605c4eaa8da66607d3c3402f7dc816 100644
--- a/content/browser/frame_host/cross_process_frame_connector.cc
+++ b/content/browser/frame_host/cross_process_frame_connector.cc
@@ -43,6 +43,7 @@ bool CrossProcessFrameConnector::OnMessageReceived(const IPC::Message& msg) {
                         OnReclaimCompositorResources)
     IPC_MESSAGE_HANDLER(FrameHostMsg_ForwardInputEvent, OnForwardInputEvent)
     IPC_MESSAGE_HANDLER(FrameHostMsg_FrameRectChanged, OnFrameRectChanged)
+    IPC_MESSAGE_HANDLER(FrameHostMsg_VisibilityChanged, OnVisibilityChanged)
     IPC_MESSAGE_HANDLER(FrameHostMsg_InitializeChildFrame,
                         OnInitializeChildFrame)
     IPC_MESSAGE_HANDLER(FrameHostMsg_SatisfySequence, OnSatisfySequence)
@@ -216,6 +217,12 @@ void CrossProcessFrameConnector::OnFrameRectChanged(
     SetSize(frame_rect);
 }
 
+void CrossProcessFrameConnector::OnVisibilityChanged(bool visible) {
+  if (!view_)
+    return;
+  view_->SetVisibility(visible);

[kenrb, 2015/11/04 21:57:42]

Why not just call Show() or Hide() directly, rather than adding a new method to
RWHVChildFrame?

[EhsanK, 2015/11/05 15:57:39]

This is a provision for <webview>.
My understanding is that those methods will get called when we call WasHidden or
WasShown on the WebContentsImpl. That being said, in case of <webview>, we will
only need to forward the call to those of the WebContentsImpl and then the
RWHVCF ones will be called. If we call Show() and Hide() directly here, and then
forward those calls to WebContentsImpl, the Show() and Hide() will get called
again (twice). That is the only reason I though of having an extra function like
this so that I can add <webview> code later in it.

I can remove but maybe add it again later when fixing the <webview> issue?

[kenrb, 2015/11/11 16:09:33]

This sounds a bit hacky, but I don't know the <webview> code well enough to
suggest anything better.

Can we still remove RWHVCF::SetVisibility() by putting the check here instead?
You should be able to call
view_->GetRenderWidgetHost()->delegate()->DidForwardVisibilityChangeToGuest(visible),
and then call Hide() or Show() directly, correct?

[EhsanK, 2015/11/11 19:13:18]

Done. I will also add Istiaque to take a look at this then.

+}
+
 void CrossProcessFrameConnector::SetDeviceScaleFactor(float scale_factor) {
   device_scale_factor_ = scale_factor;
   // The RenderWidgetHost is null in unit tests.