scheduler: Detect single event gestures correctly

scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)

Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Original-Commit-Position: refs/branch-heads/2987@{#230}
Cr-Original-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed: https://chromium.googlesource.com/chromium/src/+/6db2c563baa4b5d4dbd4bbb052db0003ea5a0f1e
Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Commit-Position: refs/branch-heads/2987@{#240}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed: https://chromium.googlesource.com/chromium/src/+/8f081a48d91e12cc9c245fb32c65c95331552677

[Sami, 2017-01-31 20:13:10]

Description was changed from

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)
==========

to

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)
==========

[Sami, 2017-01-31 20:13:10]

skyostil@chromium.org changed reviewers:
+ dtapuska@chromium.org

[Sami, 2017-01-31 20:16:01]

Description was changed from

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)
==========

to

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)

Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Commit-Position: refs/branch-heads/2987@{#230}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/6db2c563baa4b5d4dbd4bbb052db...
==========

[Sami, 2017-01-31 20:16:02]

Committed patchset #3 (id:40001) manually as
6db2c563baa4b5d4dbd4bbb052db0003ea5a0f1e (presubmit successful).

[Sami, 2017-01-31 21:10:20]

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

The reason for reverting is: Caused a test build break..

[Sami, 2017-02-01 07:06:09]

Description was changed from

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)

Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Commit-Position: refs/branch-heads/2987@{#230}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/6db2c563baa4b5d4dbd4bbb052db...
==========

to

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)

Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Commit-Position: refs/branch-heads/2987@{#230}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/6db2c563baa4b5d4dbd4bbb052db...
==========

[Sami, 2017-02-01 07:08:00]

Description was changed from

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)

Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Commit-Position: refs/branch-heads/2987@{#230}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/6db2c563baa4b5d4dbd4bbb052db...
==========

to

==========
scheduler: Detect single event gestures correctly

When a single event gesture such as a press (i.e., a single touchstart
event) is observed, the scheduler would previously wait for two
subsequent touchmove events before deciding the gesture was established
and stop blocking tasks unrelated to input handling. The problem was
that with single event gestures, these additional events are never sent,
so the scheduler would remain in 'touchstart' mode for 100ms, possibly
causing important tasks to get delayed.

This patch fixes the issue by telling the scheduler how the touchstart
event was handled. If the event handler calls preventDefault() on the
event, the scheduler can immediately conclude that the gesture is
handled by the main thread without waiting for any further events. If
preventDefault() is not called, we maintain the previous behavior.

BUG=639300
TBR=dtapuska@chromium.org

Review-Url: https://codereview.chromium.org/2661443003
Cr-Commit-Position: refs/heads/master@{#446921}
(cherry picked from commit cff6288fd965f274205ca6ab9cded462ba204dc9)

Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Original-Commit-Position: refs/branch-heads/2987@{#230}
Cr-Original-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/6db2c563baa4b5d4dbd4bbb052db...
Review-Url: https://codereview.chromium.org/2663283002 .
Cr-Commit-Position: refs/branch-heads/2987@{#240}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/8f081a48d91e12cc9c245fb32c65...
==========

[Sami, 2017-02-01 07:08:01]

Committed patchset #4 (id:60001) manually as
8f081a48d91e12cc9c245fb32c65c95331552677 (presubmit successful).