Keep track of coalesced events in main thread event queue

content/common/input_messages.h

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // IPC messages for input events and other messages that require processing in
 // order relative to input events.
 // Multiply-included message file, hence no include guard.
 
 #include "base/strings/string16.h"
 #include "build/build_config.h"
@@ skipping 118 matching lines @@
 IPC_STRUCT_TRAITS_BEGIN(content::InputEventAck)
   IPC_STRUCT_TRAITS_MEMBER(source)
   IPC_STRUCT_TRAITS_MEMBER(type)
   IPC_STRUCT_TRAITS_MEMBER(state)
   IPC_STRUCT_TRAITS_MEMBER(latency)
   IPC_STRUCT_TRAITS_MEMBER(overscroll)
   IPC_STRUCT_TRAITS_MEMBER(unique_touch_event_id)
 IPC_STRUCT_TRAITS_END()
 
 // Sends an input event to the render widget.
-IPC_MESSAGE_ROUTED3(InputMsg_HandleInputEvent,
+IPC_MESSAGE_ROUTED4(InputMsg_HandleInputEvent,
                     IPC::WebInputEventPointer /* event */,
+                    std::vector<IPC::WebInputEventPointer> /* coalesced ones*/,

[dcheng, 2017/01/23 19:38:58]

Nit: ones => events (also one space before */)

It would also be nice if the comment for this IPC message could elaborate a bit
more on what "coalesced events" are -- this could just be a pointer to another
part of the code, if it's already documented somewhere.

[Navid Zolghadr, 2017/01/23 21:42:04]

Done.

                     ui::LatencyInfo /* latency_info */,
                     content::InputEventDispatchType)
 
 // Sends the cursor visibility state to the render widget.
 IPC_MESSAGE_ROUTED1(InputMsg_CursorVisibilityChange,
                     bool /* is_visible */)
 
 // Sets the text composition to be between the given start and end offsets in
 // the currently focused editable field.
 IPC_MESSAGE_ROUTED3(InputMsg_SetCompositionFromExistingText,
@@ skipping 169 matching lines @@
 // This IPC message sends the character bounds after every composition change
 // to always have correct bound info.
 IPC_MESSAGE_ROUTED2(InputHostMsg_ImeCompositionRangeChanged,
                     gfx::Range /* composition range */,
                     std::vector<gfx::Rect> /* character bounds */)
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent InputMsg, then ifdefs for platform specific InputMsg, then
 // platform independent InputHostMsg, then ifdefs for platform specific
 // InputHostMsg.