Keep track of coalesced events in main thread event queue

components/test_runner/event_sender.cc

Index: components/test_runner/event_sender.cc
diff --git a/components/test_runner/event_sender.cc b/components/test_runner/event_sender.cc
index bcfa5f16acf0ee01c126ce55e87374acb7106586..c3a51af9a2e972fe741d2fcbee6f256a9027c4d8 100644
--- a/components/test_runner/event_sender.cc
+++ b/components/test_runner/event_sender.cc
@@ -26,8 +26,8 @@
 #include "gin/handle.h"
 #include "gin/object_template_builder.h"
 #include "gin/wrappable.h"
+#include "third_party/WebKit/public/platform/WebCoalescedInputEvent.h"
 #include "third_party/WebKit/public/platform/WebGestureEvent.h"
-#include "third_party/WebKit/public/platform/WebInputEvent.h"
 #include "third_party/WebKit/public/platform/WebPointerProperties.h"
 #include "third_party/WebKit/public/platform/WebString.h"
 #include "third_party/WebKit/public/platform/WebVector.h"
@@ -2806,7 +2806,8 @@ WebInputEventResult EventSender::HandleInputEventOnViewOrPopup(
         raw_event, delegate()->GetWindowToViewportScale());
     const WebInputEvent* popup_friendly_event =
         scaled_event.get() ? scaled_event.get() : &raw_event;
-    return popup->handleInputEvent(*popup_friendly_event);
+    return popup->handleInputEvent(
+        blink::WebCoalescedInputEvent(*popup_friendly_event));
   }
 
   std::unique_ptr<WebInputEvent> widget_event =
@@ -2814,7 +2815,7 @@ WebInputEventResult EventSender::HandleInputEventOnViewOrPopup(
   const WebInputEvent* event =
       widget_event.get() ? static_cast<WebMouseEvent*>(widget_event.get())
                          : &raw_event;
-  return widget()->handleInputEvent(*event);
+  return widget()->handleInputEvent(blink::WebCoalescedInputEvent(*event));

[dtapuska, 2017/01/13 18:56:23]

Does it not make sense here to adjust TranslateAndScaleEvent to always clone an
event and then to move the scaled event into the WebCoalescedInputEvents here?

[Navid Zolghadr, 2017/01/13 19:02:10]

I have done the modification to the generator functions in other places when in
every place we needed that cast. But in this particular case the other places
that the TransformScreenToWidgetCoordinate is used they don't all expect
WebCoalescedInputEvent.
Having said that, do you still think it is better to change that function?

[dtapuska, 2017/01/13 19:10:22]

Ugh; I had clicked on it; but it is used in a number of places so it probably
isn't best to update its signature. It is just ugly that we have a scoped_ptr
for the WebInputEvent that we can't just use if it was the right type. Oh well.

 }
 
 void EventSender::SendGesturesForMouseWheelEvent(