GitLab

The scheduler prioritizes commits when we're in a scroll and there's
a scroll handler. Today this is done by checking for scroll event
handlers in scroll begin and storing that state. It seems like we could
simply apply the scheduling strategy dynamically after scroll begin,
which allows us to remove some connections between LayerTreeHostImpl and
the ThreadedInputHandler.

Bug: 915926
Change-Id: Ic7b0c7b388f77c2f708e5f73c235a9a0e5511d1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363724
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799597}