Remove assumption that null containerForRepaint assumes RenderView

Source/core/frame/FrameView.cpp

Index: Source/core/frame/FrameView.cpp
diff --git a/Source/core/frame/FrameView.cpp b/Source/core/frame/FrameView.cpp
index 83a5bd64d7ef7c29d0db7f192cb1c0ea2f408b3d..d6d00094c6e7fd6a9430386a87301b8ec423bb5b 100644
--- a/Source/core/frame/FrameView.cpp
+++ b/Source/core/frame/FrameView.cpp
@@ -706,8 +706,11 @@ bool FrameView::hasCompositedContent() const
 
 bool FrameView::isEnclosedInCompositingLayer() const
 {
+    // FIXME: It's a bug that compositing state isn't always up to date when this is called.

[ojan, 2014/04/23 02:07:31]

Can you add to this comment a test that fails when this disabler is removed? Or,
even better, file a bug and list all the tests that fail. That way, when someone
tries to fix this in a few weeks, they'll know if they are correctly reproducing
the issue.

It's happened a bunch of times that someone removes the disabler and no tests
fail. Then that person needs to waste a bunch of time trying to figure out
what's going on.

+    DisableCompositingQueryAsserts disabler;
+
     RenderObject* frameOwnerRenderer = m_frame->ownerRenderer();
-    if (frameOwnerRenderer && frameOwnerRenderer->containerForRepaint())
+    if (frameOwnerRenderer && frameOwnerRenderer->enclosingLayer()->enclosingCompositingLayerForRepaint())
         return true;
 
     if (FrameView* parentView = parentFrameView())