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

Unified Diff: Source/core/rendering/RenderObject.cpp

Issue 233063004: Suppress layer creation for descendants of GPU-rasterized layers (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Move assert disabler in ~CompositedLayerMapping Created 6 years, 8 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/RenderObject.cpp
diff --git a/Source/core/rendering/RenderObject.cpp b/Source/core/rendering/RenderObject.cpp
index 46d7667427c235faa2e915fc37a35711f5a587cb..ca5ac633b1a864db535617ab9e6d0f370378bdff 100644
--- a/Source/core/rendering/RenderObject.cpp
+++ b/Source/core/rendering/RenderObject.cpp
@@ -1852,6 +1852,8 @@ void RenderObject::handleDynamicFloatPositionChange()
StyleDifference RenderObject::adjustStyleDifference(StyleDifference diff, unsigned contextSensitiveProperties) const
{
+ // FIXME: The calls to hasDirectReasonsForCompositing are using state that may not be up to date.
+ DisableCompositingQueryAsserts disabler;
// If transform changed, and the layer does not paint into its own separate backing, then we need to do a layout.
// FIXME: The comment above is what the code does, but it is technically not following spec. This means we will
// not to layout for 3d transforms, but we should be invoking a simplified relayout. Is it possible we are avoiding
« no previous file with comments | « Source/core/rendering/RenderLayerScrollableArea.cpp ('k') | Source/core/rendering/compositing/CompositedLayerMapping.cpp » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698