Remove updatePaintingInfoForFragments() and per-fragment shouldPaintContent flag.
It seems that all it did was to erroneously make us skip fragments. It
intersected with layer bounds, which don't include layer overflow. Before
we create the fragments in RenderMultiColumnSet, we carefully intersect
with everything relevant anyway. So rather than fixing the buggy code,
just remove it.
This means that there's no need for a per-fragment shouldPaintContent flag.
anymore.
BUG=359877
Review URL: https://codereview.chromium.org/666493002
git-svn-id: svn://svn.chromium.org/blink/trunk@184562 bbb929c8-8fbe-4397-9dbb-9b2b20218538
diff --git a/third_party/WebKit/LayoutTests/TestExpectations b/third_party/WebKit/LayoutTests/TestExpectations
index 383d4d3..b07e5a11 100644
--- a/third_party/WebKit/LayoutTests/TestExpectations
+++ b/third_party/WebKit/LayoutTests/TestExpectations
@@ -1160,6 +1160,7 @@
crbug.com/408123 fast/multicol/composited-relpos-resize.html [ Skip ]
crbug.com/408123 fast/multicol/composited-relpos.html [ Skip ]
crbug.com/408123 fast/multicol/composited-with-child-layer-in-next-column.html [ Skip ]
+crbug.com/408123 fast/multicol/composited-with-overflow-in-next-column.html [ Skip ]
crbug.com/350853 fast/multicol/content-change-same-height.html [ Skip ]
crbug.com/350853 fast/multicol/cssom-view.html [ Skip ]
crbug.com/350853 fast/multicol/inline-children-crash.html [ Skip ]
