Test synthetic pointer action on pointer event tests

Test synthetic pointer action on pointer event tests.

BUG=525187

[lanwei, 2016-09-19 16:57:17]

Description was changed from

==========
controller


 controller


 controller


 controller


 controller

BUG=
==========

to

==========
Test synthetic pointer action on pointer event tests.

BUG=525187
==========

[lanwei, 2016-09-19 16:57:17]

lanwei@chromium.org changed reviewers:
+ nzolghadr@chromium.org

[Navid Zolghadr, 2016-09-21 10:38:49]

I only commented on the files that were added on top of the other review here.

https://codereview.chromium.org/2348183003/diff/1/third_party/WebKit/LayoutTe...
File
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/pointerevent_pointermove_pointertype-manual.html
(right):

https://codereview.chromium.org/2348183003/diff/1/third_party/WebKit/LayoutTe...
third_party/WebKit/LayoutTests/imported/wpt/pointerevents/pointerevent_pointermove_pointertype-manual.html:40:
console.log('pointerdown ' + event.pointerId);
I don't think you need these logs anymore. Right?

https://codereview.chromium.org/2348183003/diff/1/third_party/WebKit/LayoutTe...
File
third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_common_input.js
(right):

https://codereview.chromium.org/2348183003/diff/1/third_party/WebKit/LayoutTe...
third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_common_input.js:59:
function mouseMoveIntoTargetGPU(targetSelector, offset=0) {
Wouldn't it be easier to just change existing mouseMoveIntoTarget function and
also just get rid of mouseClickInTarget1? or would some tests fail?

https://codereview.chromium.org/2348183003/diff/1/third_party/WebKit/LayoutTe...
third_party/WebKit/LayoutTests/imported/wpt_automation/pointerevents/pointerevent_common_input.js:159:
chrome.gpuBenchmarking.touchActionSequence(1, 0, targetRect.left +
boundaryOffset, targetRect.top + boundaryOffset, 1);
Is there a way to somehow expose these action numbers or types through some
strings? something like action number 1 ->
chrome.gpuBenchmarking.pointerAction.Press?

[lanwei, 2016-12-26 04:17:33]

The CQ bit was checked by lanwei@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-26 04:17:44]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-26 06:17:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-26 06:17:06]

Dry run: This issue passed the CQ dry run.