Bug 1642484 [wpt PR 23900] - Remove MainThreadScrollingReasons::kHasClipRelatedProper...
commit69ab27ab041d0f4c690dcd0cf33e6d72a1f92a6f
authorXianzhu Wang <wangxianzhu@chromium.org>
Mon, 8 Jun 2020 20:01:47 +0000 (8 20:01 +0000)
committerXianzhu Wang <wangxianzhu@chromium.org>
Mon, 8 Jun 2020 20:01:47 +0000 (8 20:01 +0000)
tree9f02f5adff62c6713ae2af480506b0f1c25f9b8a
parentd3e2121af6b59c4cc2f934406dd7c74da50e61c2
Bug 1642484 [wpt PR 23900] - Remove MainThreadScrollingReasons::kHasClipRelatedProperty, a=testonly

Automatic update from web-platform-tests
Remove MainThreadScrollingReasons::kHasClipRelatedProperty

We no longer need to skip composited scrolling for css clip and
clip-path since (perhaps) BlinkGenPropertyTrees.

In compositor, when we hit test on a layer with special clip/mask,
we'll still fallback to main thread hit testing/scrolling because only
the main thread knows which area is hit testable. This is achieved by
 cc::LayerTreeHostImpl::IsInitialScrollHitTestReliable() returning false.

Bug: 1074395
Change-Id: I91260b063879812ca82928fe783de25c4b6732a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225229
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774232}

--

wpt-commits: 4c2484a55b58a72b74c0b6c55ab0238cf11efb4a
wpt-pr: 23900

Differential Revision: https://phabricator.services.mozilla.com/D78793
testing/web-platform/tests/css/css-masking/clip-path/clip-path-scroll.html [new file with mode: 0644]
testing/web-platform/tests/css/css-masking/clip-path/reference/clip-path-scroll-ref.html [new file with mode: 0644]
testing/web-platform/tests/css/css-masking/clip/clip-rect-scroll.html [new file with mode: 0644]
testing/web-platform/tests/css/css-masking/clip/reference/clip-rect-scroll-ref.html [new file with mode: 0644]