Added counters for pointer boundary events fired.

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 446af06ceb533ac6c6355da509b139e620ea5a19..6635c14d1ec4f4bdaef2cef775c2d35c542c5fd3 100644
--- a/third_party/WebKit/Source/core/input/PointerEventManager.cpp
+++ b/third_party/WebKit/Source/core/input/PointerEventManager.cpp
@@ -760,11 +760,16 @@ void PointerEventManager::releasePointerCapture(int pointerId, EventTarget* targ
         releasePointerCapture(pointerId);
 }
 
-bool PointerEventManager::hasPointerCapture(int pointerId, EventTarget* target)
+bool PointerEventManager::hasPointerCapture(int pointerId, const EventTarget* target) const
 {
     return m_pendingPointerCaptureTarget.get(pointerId) == target;
 }
 
+bool PointerEventManager::hasProcessedPointerCapture(int pointerId, const EventTarget* target) const
+{
+    return m_pointerCaptureTarget.get(pointerId) == target;

[Navid Zolghadr, 2016/08/25 15:53:23]

This doesn't seem enough either. It has other blind spots. How about this:
m_pointerCaptureTarget.get(pointerId) == target && hasPointerCapture(pointerId,
target)
?

[mustaq, 2016/08/25 17:38:01]

Changed the UseCounter condition instead. I kept my API unchanged because it can
provide more info about the state of capturing. E.g.
- hasPointerCapture XOR hasProcessedCapturing means transient state,
- !hasPointerCapture AND hasProcessedCapturing means "about to lose capture"
state etc.

+}
+
 void PointerEventManager::releasePointerCapture(int pointerId)
 {
     m_pendingPointerCaptureTarget.remove(pointerId);