Index: LayoutTests/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt |
diff --git a/LayoutTests/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt b/LayoutTests/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt |
index 1b4251bd7504251b26066159b5190c340d432fa1..5038d4c1fb26841405e9b0e354549e0a488605ff 100644 |
--- a/LayoutTests/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt |
+++ b/LayoutTests/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: |
{ |