GitLab

The behavior in this test differs based on main thread and compositor
thread scrolling. On the compositor thread, only the direct-most hit
scroller is targeted for autoscrolling but the main thread will bubble
up to the first scroller that can consume the scroll. See the
autoscroll-related comment in LayerTreeHostImpl::FindNodeToLatch.

The compositor behavior is the intended one, see
https://crrev.com/c/1743028 which implemented this behavior on both
threads and added a test that was unfortunately removed in
https://crrev.com/c/2111831. The test in this CL covers this case just
as well so we just move it to fast/scrolling to ensure it gets coverage
on both compositor and main threads.

Bug: 915926,1112183
Change-Id: I2dcc4e83d30dbc222cefc1781b5ecf46b20a3f85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441941Reviewed-by: Rahul Arakeri <arakeri@microsoft.com>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#812830}