Don't force layout for mouse event hit tests

Tools/DumpRenderTree/chromium/TestRunner/src/EventSender.h

Index: Tools/DumpRenderTree/chromium/TestRunner/src/EventSender.h
diff --git a/Tools/DumpRenderTree/chromium/TestRunner/src/EventSender.h b/Tools/DumpRenderTree/chromium/TestRunner/src/EventSender.h
index 9b36b5fc31aa39d7be77fec7670d921243e93f36..009f595ae2857f2e3095cff544692a99077e4fb2 100644
--- a/Tools/DumpRenderTree/chromium/TestRunner/src/EventSender.h
+++ b/Tools/DumpRenderTree/chromium/TestRunner/src/EventSender.h
@@ -122,6 +122,10 @@ public:
     void gestureTwoFingerTap(const CppArgumentList&, CppVariant*);
     void gestureEvent(WebKit::WebInputEvent::Type, const CppArgumentList&);
 
+    // Setting this to false makes EventSender not force layout() calls.
+    // This makes it possible to test the standard WebCore event dispatch.
+    CppVariant forceLayoutOnEvents;
+
     // Unimplemented stubs
     void enableDOMUIEventLogging(const CppArgumentList&, CppVariant*);
     void fireKeyboardEventsToElement(const CppArgumentList&, CppVariant*);
@@ -147,6 +151,8 @@ private:
     // Returns true if dragMode is true.
     bool isDragMode() { return dragMode.isBool() && dragMode.toBoolean(); }
 
+    bool shouldForceLayoutOnEvents() const { return forceLayoutOnEvents.isBool() && forceLayoutOnEvents.toBoolean(); }
+
     // Sometimes we queue up mouse move and mouse up events for drag drop
     // handling purposes. These methods dispatch the event.
     void doMouseMove(const WebKit::WebMouseEvent&);