Revert "Ensure that TouchEvents are always async after scrolling has started."
This reverts commit f4886cba. Reason for revert: This causes unintended throttling of TouchMoves if the page is at the overflow already. Fix will land in next release. See crbug/1123304 for details. Original change's description: > Ensure that TouchEvents are always async after scrolling has started. > > Currently we can flip flop back and forth between TouchMoves being sent > async or sync which can cause some pretty noticeable cases of jank. This > ensures that we are always consistently scrolling after deciding > TouchMoves can be async. > > Bug: 1072364 > Change-Id: I3ef1ed6715d4b1fd2d3e1377ebd6b0c8bcc02872 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2182426 > Commit-Queue: Stephen Nusko <nuskos@chromium.org> > Auto-Submit: Stephen Nusko <nuskos@chromium.org> > Reviewed-by: David Bokan <bokan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#776487} TBR=bokan@chromium.org,nuskos@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1072364,1123304 Change-Id: I7645aa130ddaf5214bde77a8cbcdd239e48f729c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413491 Auto-Submit: Stephen Nusko <nuskos@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:David Bokan <bokan@chromium.org> Reviewed-by:
Stephen Nusko <nuskos@chromium.org> Cr-Commit-Position: refs/heads/master@{#807464}
Showing
Please register or sign in to comment