Add setVisibilityState API to WebFrameWidget

Source/web/WebFrameWidgetImpl.cpp

Index: Source/web/WebFrameWidgetImpl.cpp
diff --git a/Source/web/WebFrameWidgetImpl.cpp b/Source/web/WebFrameWidgetImpl.cpp
index df861ab42c9374debbbb3dc1fdb3eef2367b3741..251b1ef12db24401d1e3e63d6272c17cc7c18de7 100644
--- a/Source/web/WebFrameWidgetImpl.cpp
+++ b/Source/web/WebFrameWidgetImpl.cpp
@@ -1014,4 +1014,18 @@ void WebFrameWidgetImpl::setRootGraphicsLayer(GraphicsLayer* layer)
     suppressInvalidations(false);
 }
 
+void WebFrameWidgetImpl::setVisibilityState(WebPageVisibilityState visibilityState, bool isInitialState)
+{
+    if (!m_page)
+        return;
+
+    ASSERT(visibilityState == WebPageVisibilityStateVisible || visibilityState == WebPageVisibilityStateHidden || visibilityState == WebPageVisibilityStatePrerender);

[Nate Chapin, 2015/02/26 21:16:34]

I agree this is wonky, but if there's precedent, I'll get over it.

[kenrb, 2015/02/26 22:29:56]

Or, I could just remove it. There is nothing I can find to suggest a really good
reason.

+    m_page->setVisibilityState(static_cast<PageVisibilityState>(visibilityState), isInitialState);

[Nate Chapin, 2015/02/26 21:16:34]

Just to make sure I understand correctly, setVisibilityState() is only called on
one WebFrameWidget per page?

[kenrb, 2015/02/26 22:29:56]

Aha, no. :(

This is what I was talking about before with confusion of page and frame level
visibility state. This has the potential to cause some visual issues when you
have multiple OOPIFs in the same process -- the Page will temporarily think it
is invisible while one OOPIF is being loaded, even though another OOPIF might be
available and rendering.

Are you okay with this if I file a bug against myself to sort this out later?

+
+    if (m_layerTreeView) {
+        bool visible = visibilityState == WebPageVisibilityStateVisible;
+        m_layerTreeView->setVisible(visible);
+    }
+}
+
 } // namespace blink