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

Unified Diff: LayoutTests/platform/android/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt

Issue 898783003: Move rendering/RenderLayer* to layout/ (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 5 years, 10 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: LayoutTests/platform/android/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt
diff --git a/LayoutTests/platform/android/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt b/LayoutTests/platform/android/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt
index 8bc591dd223c0e8d4c15c78d9178dcd4d3fd472f..7a74541ac627896f8a11bccc0bd6bb1bbead0055 100644
--- a/LayoutTests/platform/android/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt
+++ b/LayoutTests/platform/android/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt
@@ -1,4 +1,4 @@
-A squashing RenderLayer that becomes non-composited should correctly send a repaint invalidation to the new container GraphicsLayer that it paints into. When run interactively, hovering over the force-composited gray div should not cause other layers to disappear.
+A squashing Layer that becomes non-composited should correctly send a repaint invalidation to the new container GraphicsLayer that it paints into. When run interactively, hovering over the force-composited gray div should not cause other layers to disappear.
CASE 1, original layer tree:
{

Powered by Google App Engine
This is Rietveld 408576698