FullyInvalidatePaint should not be called for CompositeAfterPaint

There is a DisableCompositingQueryAsserts in
LayoutView::InvalidatePaintForViewAndCompositedLayers, however for
CompositeAfterPaint, there is no CompositedLayerMapping to invalidate.
In this case, the call to SetSubtreeShouldDoFullPaintInvalidation
sets up state so that all necessary invalidation computed in the
pre-paint walk.

Bug: 1007989
Change-Id: I7dcf39fc8473baa5aa0a9e4dd3c28cd588562a20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899902Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Daniel Libby <dlibby@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#714049}

third_party/blink/renderer/core/layout/layout_view.cc

@@ -462,12 +462,11 @@ void LayoutView::SetShouldDoFullPaintInvalidationForViewAndAllDescendants() {
 void LayoutView::InvalidatePaintForViewAndCompositedLayers() {
   SetSubtreeShouldDoFullPaintInvalidation();
 
-  // The only way we know how to hit these ASSERTS below this point is via the
-  // Chromium OS login screen.
+  if (!RuntimeEnabledFeatures::CompositeAfterPaintEnabled()) {
     DisableCompositingQueryAsserts disabler;
-
     if (Compositor()->InCompositingMode())
       Compositor()->FullyInvalidatePaint();
+  }
 }
 
 bool LayoutView::MapToVisualRectInAncestorSpace(

third_party/blink/renderer/core/paint/compositing/paint_layer_compositor.cc

@@ -652,6 +652,8 @@ static void FullyInvalidatePaintRecursive(PaintLayer* layer) {
 }
 
 void PaintLayerCompositor::FullyInvalidatePaint() {
+  DCHECK(!RuntimeEnabledFeatures::CompositeAfterPaintEnabled());
+
   // We're walking all compositing layers and invalidating them, so there's
   // no need to have up-to-date compositing state.
   DisableCompositingQueryAsserts disabler;