Move updateLayout() call from RenderLayer to RenderView

Source/core/rendering/RenderView.cpp

Index: Source/core/rendering/RenderView.cpp
diff --git a/Source/core/rendering/RenderView.cpp b/Source/core/rendering/RenderView.cpp
index 5cb83eec3c388313602195bed1ee72a367b8c4b2..3133d7825c1d30980949ea329f598b3e795b682b 100644
--- a/Source/core/rendering/RenderView.cpp
+++ b/Source/core/rendering/RenderView.cpp
@@ -87,6 +87,10 @@ bool RenderView::hitTest(const HitTestRequest& request, HitTestResult& result)
 
 bool RenderView::hitTest(const HitTestRequest& request, const HitTestLocation& location, HitTestResult& result)
 {
+    // We have to recursively update layout/style here because otherwise, when the hit test recurses
+    // into a child document, it could trigger a layout on the parent document, which can destroy RenderLayers

[ojan, 2013/05/16 23:57:54]

When does hit-testing in a child document trigger a layout in the parent
document? I expect this code is right, I just want to understand the codepath
that requires the recursive bit before lgtm'ing.

[cbiesinger, 2013/05/17 00:17:04]

Document::updateLayout calls updateLayout on its parent:
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit...

But now that you ask, I don't fully understand why that is a problem... I think
I need to spend more time in gdb.

+    // that are higher up in the call stack, leading to crashes.
+    frameView()->updateLayoutAndStyleIfNeededRecursive();
     return layer()->hitTest(request, location, result);
 }