chromium/src/third_party/blink/web_tests/flag-specific/composite-after-paint/compositing/squashing/squashed-layer-loses-graphicslayer-expected.txt

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:
{
  "layers": [
    {
      "name": "Scrolling background of LayoutView #document",
      "bounds": [800, 600],
      "contentsOpaque": true,
      "backgroundColor": "#FFFFFF"
    },
    {
      "name": "LayoutNGBlockFlow (positioned) DIV id='forceComposited' class='composited underneath'",
      "bounds": [100, 100],
      "contentsOpaque": true,
      "backgroundColor": "#808080",
      "transform": 1
    },
    {
      "name": "LayoutNGBlockFlow (positioned) DIV id='A' class='overlap1'",
      "position": [140, 140],
      "bounds": [260, 260],
      "contentsOpaqueForText": true
    }
  ],
  "transforms": [
    {
      "id": 1,
      "transform": [
        [1, 0, 0, 0],
        [0, 1, 0, 0],
        [0, 0, 1, 0],
        [60, 60, 0, 1]
      ]
    }
  ]
}

CASE 2, The original composited layer is no longer composited, which then also removes all squashing layers. The important point is that there should be an appropriate repaint to the root GraphicsLayer:
{
  "layers": [
    {
      "name": "Scrolling background of LayoutView #document",
      "bounds": [800, 600],
      "contentsOpaque": true,
      "backgroundColor": "#FFFFFF",
      "invalidations": [
        [300, 300, 100, 100],
        [220, 220, 100, 100],
        [140, 140, 100, 100],
        [60, 60, 100, 100]
      ]
    }
  ]
}