Move touch hit testing to PointerEventManager

third_party/WebKit/Source/core/input/TouchEventManager.h

Index: third_party/WebKit/Source/core/input/TouchEventManager.h
diff --git a/third_party/WebKit/Source/core/input/TouchEventManager.h b/third_party/WebKit/Source/core/input/TouchEventManager.h
index 6de6c5641c11978ca3a4d2a29b89599238de6363..e62e110cd0c8180b845618bc5228a979c6e7efba 100644
--- a/third_party/WebKit/Source/core/input/TouchEventManager.h
+++ b/third_party/WebKit/Source/core/input/TouchEventManager.h
@@ -40,7 +40,6 @@ public:
         FloatPoint adjustedPagePoint;
         FloatSize adjustedRadius;
         bool knownTarget;
-        bool consumed;

[mustaq, 2016/05/11 14:30:55]

I don't think we can afford to lose this until crbug.com/607588 is fixed. You
can either bring it back, or delay this CL until after the other bug is fixed.

[Navid Zolghadr, 2016/05/11 16:43:42]

Let's discuss this offline in more details. But I believe this should cause any
difficulty for that. This CL just uses another mechanism for preventing the
touch event and bypassing that will be easy. That mechanism lives in
PointerEventManager.

         String region;
     };
 
@@ -48,14 +47,15 @@ public:
     ~TouchEventManager();
     DECLARE_TRACE();
 
-    // Returns true if it succesfully generates touchInfos.
-    bool generateTouchInfosAfterHittest(
+    // Does the hit-testing again if the original hit test result was not inside
+    // capturing frame for touch events.
+    bool reHitTestTouchPointsIfNeeded(
         const PlatformTouchEvent&,
         HeapVector<TouchInfo>&);
 
     WebInputEventResult handleTouchEvent(
         const PlatformTouchEvent&,
-        const HeapVector<TouchInfo>&);
+        HeapVector<TouchInfo>&);
 
     // Resets the internal state of this object.
     void clear();