[SPv2] Defer decision of raster invalidation after paint for changes z-index, transform, etc.

third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2

Index: third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2
diff --git a/third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2 b/third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2
index 096abb6fa9b004bd4ef3c3c1e10fdc37414451af..a58c91c7788df4f78be57ce30ae21faa6f33b062 100644
--- a/third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2
+++ b/third_party/WebKit/LayoutTests/FlagExpectations/enable-slimming-paint-v2
@@ -600,6 +600,7 @@ fast/clip/overflow-border-radius-fixed-position.html [ Failure ]
 fast/clip/overflow-border-radius-transformed.html [ Failure ]
 fast/css-generated-content/014.html [ Failure ]
 fast/css-generated-content/table-parts-before-and-after.html [ Failure ]
+fast/css-grid-layout/grid-item-z-index-change-repaint.html [ Failure ]

[chrishtr, 2016/09/07 20:49:02]

These are marked as Failure because they invalidate
differently, right? Should these be part of the virtual test
suite with different expectations perhaps?

[Xianzhu, 2016/09/07 21:38:35]

Yes.
There are also many other repaint tests having the similar issue. I think it's a
good way to run them as virtual tests with new baselines.

[pdr., 2016/09/08 01:36:23]

There are about 426 repaint tests in fast/ (43 outside fast/repaint) and another
534 repaint tests in svg/ (490 outside svg/repaint) so we're talking about a lot
of tests to maintain.

I don't have a great plan for this. What if we moved all repaint tests to a
repaint/ directory and just ran those directories as virtual tests suites? Do
you have a feeling for how many failures we would need to initially add to
TestExpectations for that to work?

[Xianzhu, 2016/09/08 03:01:42]

I planned to move all repaint tests to paint/invalidation directory, but haven't
found a time to do it yet. It might be a proper time to do this after this CL.
When moving them, I would generate new baselines instead of adding them to
TestExpectations. We can verify the validity of the new baselines after we get
raster-invalidation raster-under-invalidation-checking work.

 fast/css-grid-layout/min-width-height-auto-overflow.html [ Failure ]
 fast/css-grid-layout/scrolled-grid-painting-overflow.html [ Failure ]
 fast/css-grid-layout/scrolled-grid-painting.html [ Failure ]
@@ -1192,6 +1193,7 @@ fast/repaint/filter-invalidation-with-composited-container-change.html [ Failure
 fast/repaint/filter-repaint-accelerated-child-with-filter-child.html [ Failure ]
 fast/repaint/filter-repaint-accelerated-on-accelerated-filter.html [ Failure ]
 fast/repaint/filter-repaint-on-accelerated-layer.html [ Failure ]
+fast/repaint/fixed-after-scroll.html [ Failure ]
 fast/repaint/fixed-and-absolute-position-scrolled.html [ Failure ]
 fast/repaint/fixed-child-move-after-scroll.html [ Failure ]
 fast/repaint/fixed-child-of-fixed-move-after-scroll.html [ Failure ]
@@ -1200,6 +1202,7 @@ fast/repaint/fixed-element-repaint-after-compositing-update.html [ Failure ]
 fast/repaint/fixed-in-page-scale.html [ Crash Timeout ]
 fast/repaint/fixed-move-after-scroll.html [ Failure ]
 fast/repaint/fixed-right-bottom-in-page-scale.html [ Crash Timeout ]
+fast/repaint/fixed-to-relative-position-with-absolute-child.html [ Failure ]
 fast/repaint/fixed-tranformed.html [ Failure ]
 fast/repaint/fixed-under-composited-absolute-scrolled.html [ Failure ]
 fast/repaint/fixed-under-composited-fixed-scrolled.html [ Failure ]
@@ -1225,6 +1228,7 @@ fast/repaint/line-flow-with-floats-6.html [ Failure ]
 fast/repaint/line-flow-with-floats-7.html [ Failure ]
 fast/repaint/line-flow-with-floats-8.html [ Failure ]
 fast/repaint/line-flow-with-floats-9.html [ Failure ]
+fast/repaint/mix-blend-mode-separate-stacking-context.html [ Failure ]
 fast/repaint/multicol-as-paint-container.html [ Failure ]
 fast/repaint/multicol-nested.html [ Failure ]
 fast/repaint/multicol-repaint.html [ Failure ]