FrameSelection::updateApperance for caret should not cause layout.

Source/web/WebViewImpl.cpp

Index: Source/web/WebViewImpl.cpp
diff --git a/Source/web/WebViewImpl.cpp b/Source/web/WebViewImpl.cpp
index 9f8c31ff244cd5c6fcd84ac10f547d188cc6ce3f..f0f07270ef513d36f1c3fcfa83807f2aa37a1418 100644
--- a/Source/web/WebViewImpl.cpp
+++ b/Source/web/WebViewImpl.cpp
@@ -1742,6 +1742,10 @@ void WebViewImpl::beginFrame(const WebBeginFrameArgs& frameTime)
         ContinuousPainter::setNeedsDisplayRecursive(m_rootGraphicsLayer, m_pageOverlays.get());
         m_client->scheduleAnimation();
     }
+
+    const Frame* frame = focusedWebCoreFrame();
+    if (frame && frame->isLocalFrame())
+        toLocalFrame(frame)->selection().recomputeCaretRect();

[abarth-chromium, 2014/08/09 19:05:09]

This is much too early.  What if the GraphicsLayer for the caret gets created or
destroyed during the compositing update?  We want to do this work when the
DocumentLifecycle is InPaintInvalidation.

 }
 
 void WebViewImpl::layout()