Support Coalesced Touch in ppapi

third_party/WebKit/Source/core/input/PointerEventManager.cpp

Index: third_party/WebKit/Source/core/input/PointerEventManager.cpp
diff --git a/third_party/WebKit/Source/core/input/PointerEventManager.cpp b/third_party/WebKit/Source/core/input/PointerEventManager.cpp
index 51501f37e039a2bf257d43cb321a63cd0b8543d6..5afea17ea3b4f78c38712e9f2a45f1e453ecf887 100644
--- a/third_party/WebKit/Source/core/input/PointerEventManager.cpp
+++ b/third_party/WebKit/Source/core/input/PointerEventManager.cpp
@@ -318,7 +318,8 @@ WebInputEventResult PointerEventManager::HandleTouchEvents(
 
   DispatchTouchPointerEvents(event, coalesced_events, touch_infos);
 
-  return touch_event_manager_->HandleTouchEvent(event, touch_infos);
+  return touch_event_manager_->HandleTouchEvent(event, coalesced_events,

[Navid Zolghadr, 2017/05/01 15:53:33]

This is unlikely that we keep this coalesced_events variable here as we are in
the process of removing the coalesced touch events altogether and just keep the
coalesced pointer events. In that case we will not have the grouping for the
coalesced touch events anymore.

[jkwang, 2017/05/02 18:59:15]

Is there a time line of removing coalesced touch events?
If coalesced touch event is not available any more. We can build the touch
events from coalesced pointer events. The goal is to report the trace of all
touch points, so we can see touch event as a snapshot of "multiple pointer event
streams". 
I am not sure what I can do now to make things easier(and correct). But if we
can make the change when we remove the coalesced touch events, I think it's OK
to leave it like this. 

+                                                touch_infos);
 }
 
 void PointerEventManager::ComputeTouchTargets(