Revert "Don't force layout for mouse event hit tests"

Source/core/page/EventHandler.cpp

Index: Source/core/page/EventHandler.cpp
diff --git a/Source/core/page/EventHandler.cpp b/Source/core/page/EventHandler.cpp
index 15ea82a086bd41e8ed86778eea4e04925c083539..f47fde534b9e0c3bc198c70616fe56af794e12fd 100644
--- a/Source/core/page/EventHandler.cpp
+++ b/Source/core/page/EventHandler.cpp
@@ -926,13 +926,7 @@ HitTestResult EventHandler::hitTestResultAtPoint(const LayoutPoint& point, HitTe
 
     HitTestResult result(point, padding.height(), padding.width(), padding.height(), padding.width());
 
-    // RenderView::hitTest causes a layout, and we don't want to hit that until the first
-    // layout because until then, there is nothing shown on the screen - the user can't
-    // have intentionally clicked on something belonging to this page. Furthermore,
-    // mousemove events before the first layout should not lead to a premature layout()
-    // happening, which could show a flash of white.
-    // See also the similar code in Document::prepareMouseEvent.
-    if (!m_frame->contentRenderer() || !m_frame->view() || !m_frame->view()->didFirstLayout())
+    if (!m_frame->contentRenderer())
         return result;
 
     // hitTestResultAtPoint is specifically used to hitTest into all frames, thus it always allows child frame content.