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

Unified Diff: Source/core/rendering/compositing/GraphicsLayerUpdater.cpp

Issue 358153003: Get rid of one-off paint invalidation code for paints-into-ancestor compositing state (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Addressed comment from vollick@ Created 6 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: Source/core/rendering/compositing/GraphicsLayerUpdater.cpp
diff --git a/Source/core/rendering/compositing/GraphicsLayerUpdater.cpp b/Source/core/rendering/compositing/GraphicsLayerUpdater.cpp
index 9bbf3a2d3a8c57ef120b9e3e595aaf5830eb4e77..d1335b4f2eea514e37a495f3020d00ad72119a3b 100644
--- a/Source/core/rendering/compositing/GraphicsLayerUpdater.cpp
+++ b/Source/core/rendering/compositing/GraphicsLayerUpdater.cpp
@@ -92,8 +92,10 @@ void GraphicsLayerUpdater::updateRecursive(RenderLayer& layer, UpdateType update
const RenderLayer* compositingContainer = context.compositingContainer(layer);
ASSERT(compositingContainer == layer.ancestorCompositingLayer());
- if (mapping->updateRequiresOwnBackingStoreForAncestorReasons(compositingContainer))
+ if (mapping->updateRequiresOwnBackingStoreForAncestorReasons(compositingContainer)) {
+ layersNeedingPaintInvalidation.append(&layer);
updateType = ForceUpdate;
+ }
// Note carefully: here we assume that the compositing state of all descendants have been updated already,
// so it is legitimate to compute and cache the composited bounds for this layer.

Powered by Google App Engine
This is Rietveld 408576698