Fix clientX/Y properties of touch pointer events

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..6f1e5e307788ca1a2196176b79cf05d849cb393b 100644
--- a/third_party/WebKit/Source/core/input/TouchEventManager.h
+++ b/third_party/WebKit/Source/core/input/TouchEventManager.h
@@ -37,7 +37,8 @@ public:
         PlatformTouchPoint point;
         Member<Node> touchNode;
         Member<LocalFrame> targetFrame;
-        FloatPoint adjustedPagePoint;
+        FloatPoint clientPoint;

[mustaq, 2016/05/09 14:49:05]

bokan@: "client" seems to be an overloaded term throughout our codebase. May be
this is not true for coordinates? Any chance we could be more specific here?

[Navid Zolghadr, 2016/05/09 17:01:43]

bokan@, do you think framePoint is better instead of clientPoint here or maybe
totally something else?

[bokan, 2016/05/09 17:17:47]

Client and Frame are interchangeable. In terms of coordinates its not overloaded
and is a necessity since lots of web facing APIs use clientX/Y so we have to
keep it in some places.

I don't have a strong preference either way. If this isn't web facing though,
framePoint is generally used for chrome internal data. If you do keep it
clientPoint, then you should change contentPoint below to pagePoint to match.

+        FloatPoint contentPoint;
         FloatSize adjustedRadius;
         bool knownTarget;
         bool consumed;