Enable VsyncAlignedInput to Field Trial

Enable VsyncAlignedInput to field trial

Enable Field Trial on Android, ChromeOS, Linux, Mac, Win.

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|, which 
means the ack will come back later and the generated |GestureScrollUpdate| will falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame with or 
without this patch.

BUG=704134
Review-Url: https://codereview.chromium.org/2752363002
Cr-Commit-Position: refs/heads/master@{#458921}
Committed: https://chromium.googlesource.com/chromium/src/+/5a7f45dab8372cb7b80ee24dfb137a7ced2049ea

[chongz, 2017-03-22 15:21:07]

Patchset #1 (id:1) has been deleted

[chongz, 2017-03-22 15:41:22]

Description was changed from

==========
Enable VsyncAlignedInput to field trial

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

to

==========
Enable VsyncAlignedInput to field trial

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134
==========

[chongz, 2017-03-22 15:55:01]

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

[commit-bot: I haz the power, 2017-03-22 15:55:25]

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

[chongz, 2017-03-22 16:02:02]

Description was changed from

==========
Enable VsyncAlignedInput to field trial

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134
==========

to

==========
Enable VsyncAlignedInput to field trial

Enable Field Trial on ChromeOS, Linux, Mac, Win.
(No Android as we don't have simulation for Android unbuffered input)

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134
==========

[chongz, 2017-03-22 16:07:19]

Description was changed from

==========
Enable VsyncAlignedInput to field trial

Enable Field Trial on ChromeOS, Linux, Mac, Win.
(No Android as we don't have simulation for Android unbuffered input)

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134
==========

to

==========
Enable VsyncAlignedInput to field trial

Enable Field Trial on Android, ChromeOS, Linux, Mac, Win.

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134
==========

[commit-bot: I haz the power, 2017-03-22 16:42:01]

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

[commit-bot: I haz the power, 2017-03-22 16:42:01]

Dry run: This issue passed the CQ dry run.

[chongz, 2017-03-22 16:57:00]

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

[commit-bot: I haz the power, 2017-03-22 16:57:15]

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

[chongz, 2017-03-22 16:58:03]

Patchset #1 (id:20001) has been deleted

[commit-bot: I haz the power, 2017-03-22 17:51:52]

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

[commit-bot: I haz the power, 2017-03-22 17:51:53]

Dry run: This issue passed the CQ dry run.

[chongz, 2017-03-22 17:55:46]

chongz@chromium.org changed reviewers:
+ isherman@chromium.org

[chongz, 2017-03-22 17:55:47]

isherman@ PTAL, thanks!

[Ilya Sherman, 2017-03-22 21:37:54]

lgtm

[chongz, 2017-03-22 23:06:27]

The CQ bit was checked by chongz@chromium.org

[commit-bot: I haz the power, 2017-03-22 23:07:52]

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, 2017-03-22 23:13:20]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1490223987370520,
"parent_rev": "1139825719f0479bc40151d88e8bb416bafad5eb", "commit_rev":
"5a7f45dab8372cb7b80ee24dfb137a7ced2049ea"}

[commit-bot: I haz the power, 2017-03-22 23:14:07]

Description was changed from

==========
Enable VsyncAlignedInput to field trial

Enable Field Trial on Android, ChromeOS, Linux, Mac, Win.

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134
==========

to

==========
Enable VsyncAlignedInput to field trial

Enable Field Trial on Android, ChromeOS, Linux, Mac, Win.

This patch will cause expected 1 frame delay in 
"scheduler.tough_scheduling_cases.first_gesture_scroll_update_latency".

Reasons for the delay:
The synthetic input controller sends |TouchMove| right before |BeginFrame|,
which 
means the ack will come back later and the generated |GestureScrollUpdate| will
falls
into next |BeginFrame|.

This is fine since the actual scroll result won't be rendered until next frame
with or 
without this patch.

BUG=704134

Review-Url: https://codereview.chromium.org/2752363002
Cr-Commit-Position: refs/heads/master@{#458921}
Committed:
https://chromium.googlesource.com/chromium/src/+/5a7f45dab8372cb7b80ee24dfb13...
==========

[commit-bot: I haz the power, 2017-03-22 23:14:08]

Committed patchset #1 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/5a7f45dab8372cb7b80ee24dfb13...

[chongz, 2017-03-31 18:52:12]

A revert of this CL (patchset #1 id:40001) has been created in
https://codereview.chromium.org/2791663002/ by chongz@chromium.org.

The reason for reverting is: Reverting due to issue 704732. Will try to find the
root cause before re-landing..