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..f221eb33313e603a43df778dd575045855fbe5d6 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 framePoint;
+        FloatPoint contentPoint;

[bokan, 2016/05/09 18:13:08]

Since we have a reference to the targetFrame above, would it make more sense to
keep just one of these and add an accessor for the other that just calculates
using contentsToFrame/frameToContents. That way they can't ever be out of sync.

[Navid Zolghadr, 2016/05/09 18:59:04]

Sure. I was going to remove this whole struct in the later change but it sure is
better to avoid adding redundant stuff here until it gets removed.

         FloatSize adjustedRadius;
         bool knownTarget;
         bool consumed;