Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(422)

Issue 2310203002: Invalidate scrolling contents layer background when child invalidated. (Closed)

Created:
4 years, 3 months ago by flackr
Modified:
4 years, 3 months ago
Reviewers:
chrishtr
CC:
blink-reviews, blink-reviews-paint_chromium.org, chromium-reviews, dshwang, slimming-paint-reviews_chromium.org
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Invalidate scrolling contents layer background when child invalidated. BUG=643741 TEST=paint/invalidation/selection-within-opaque-composited-scroller.html CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+19 lines, -5 lines) Patch
A + third_party/WebKit/LayoutTests/paint/invalidation/selection-within-opaque-composited-scroller.html View 1 chunk +11 lines, -4 lines 0 comments Download
A + third_party/WebKit/LayoutTests/paint/invalidation/selection-within-opaque-composited-scroller-expected.txt View 3 chunks +5 lines, -1 line 0 comments Download
M third_party/WebKit/Source/core/paint/ObjectPaintInvalidator.cpp View 1 chunk +3 lines, -0 lines 0 comments Download

Messages

Total messages: 3 (2 generated)
flackr
4 years, 3 months ago (2016-09-06 19:30:34 UTC) #3
Hey Chris,

I was having a closer look at exactly what the difference was in this particular
test case. It seems that a child of the composited scroller is updated, and then
we have an invalid display item on the composited scroller. Does it make sense
that we would need to invalidate the composited scroller when it paints the
background and a child of it is updated? This does fix my test case.

PTAL, thanks.

Powered by Google App Engine
This is Rietveld 408576698