Rename SyntheticPointer to SyntheticPointerDriver

content/browser/renderer_host/input/synthetic_touch_driver.h

+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CONTENT_BROWSER_RENDERER_HOST_INPUT_SYNTHETIC_TOUCH_DRIVER_H_
+#define CONTENT_BROWSER_RENDERER_HOST_INPUT_SYNTHETIC_TOUCH_DRIVER_H_
+
+#include <array>
+#include "base/macros.h"
+#include "content/browser/renderer_host/input/synthetic_pointer_driver.h"
+#include "content/common/content_export.h"
+#include "content/common/input/synthetic_web_input_event_builders.h"
+
+namespace content {
+
+class CONTENT_EXPORT SyntheticTouchDriver : public SyntheticPointerDriver {
+ public:
+  SyntheticTouchDriver();
+  explicit SyntheticTouchDriver(SyntheticWebTouchEvent touch_event);
+  ~SyntheticTouchDriver() override;
+
+  void DispatchEvent(SyntheticGestureTarget* target,
+                     const base::TimeTicks& timestamp) override;
+
+  int Press(float x, float y) override;
+  void Move(float x, float y, int index) override;
+  void Release(int index) override;
+
+  bool UserInputCheck(
+      const SyntheticPointerActionParams& params) const override;
+
+ private:
+  SyntheticWebTouchEvent touch_event_;

[tdresser, 2016/11/10 14:58:32]

I'm a bit worried that the implementation of SyntheticWebTouchEvent is robust
enough to expose to developers, but that's a separate patch.

I'm not convinced it actually manages the index correctly in cases such as:
Press finger 1.
Press finger 2.
Release finger 2.
Press finger 2.
Release finger 2.
Press finger 2.
Release finger 2.

Can you take a look at how we behave in that case, and make sure it works
correctly?

[lanwei, 2016/11/10 19:45:22]

It works fine, I added a test.

+  DISALLOW_COPY_AND_ASSIGN(SyntheticTouchDriver);
+};
+
+}  // namespace content
+
+#endif  // CONTENT_COMMON_INPUT_SYNTHETIC_TOUCH_DRIVER_H_