Add the rest of web platform pointerevent tests

third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_touch-action-button-test_touch-manual-input.js

Index: third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_touch-action-button-test_touch-manual-input.js
diff --git a/third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_touch-action-button-test_touch-manual-input.js b/third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_touch-action-button-test_touch-manual-input.js
new file mode 100644
index 0000000000000000000000000000000000000000..d972b5a3f8dad5862a0c318738862da4462c6140
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_touch-action-button-test_touch-manual-input.js
@@ -0,0 +1,8 @@
+importAutomationScript('/pointerevents/pointerevent_common_input.js');
+
+function inject_input() {
+  touchScrollUpInTarget('target0');
+  touchScrollLeftInTarget('target0');
+  touchTapInTarget('btnComplete');

[Rick Byers, 2016/07/05 15:01:30]

I was originally surprised that this works.  The gpubenchmarking commands are
asynchronous, so when we execute touchTapInTarget the scroll hasn't occurred
yet, so we're getting the client co-ordinates of the button prior to the scroll.
 But of course in this case we're scrolling a div, not the document, so the
client co-ords aren't invalidated.

Aren't there already cases where we want to scroll the document and then tap
somewhere in the document?  If not, I'm sure there will be at some point.  How
will we handle those?

In general, I believe we're eventually going to hit a case where we really to
write these tests in a fully async style - eg. by chaining promises.  I'm fine
putting this off for now, but we should definitely keep our eye out for when
we'll really need it.

[Navid Zolghadr, 2016/07/05 15:42:20]

I see. There might be some problems already as I have skipped a few of these
touch tests due to some crashes. However, I don't think the current APIs like
tap returns a promise. Right? But if I'm not mistaken they did have a callback
parameter. So I guess I can use the callback parameter to do that
synchronization. Would that be okay?

+}
+