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

Side by Side Diff: LayoutTests/virtual/softwarecompositing/squashing/squashed-layer-loses-graphicslayer-expected.txt

Issue 473473003: Remove virtual/softwarecompositing suite (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Rebase Created 6 years, 4 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 unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 A squashing RenderLayer that becomes non-composited should correctly send a repa int invalidation to the new container GraphicsLayer that it paints into. When ru n interactively, hovering over the force-composited gray div should not cause ot her layers to disappear.
2
3 CASE 1, original layer tree:
4 {
5 "bounds": [800, 600],
6 "children": [
7 {
8 "bounds": [800, 600],
9 "contentsOpaque": true,
10 "drawsContent": true,
11 "children": [
12 {
13 "children": [
14 {
15 "position": [60, 60],
16 "bounds": [100, 100],
17 "contentsOpaque": true,
18 "drawsContent": true,
19 "backgroundColor": "#808080"
20 },
21 {
22 "position": [140, 140],
23 "bounds": [260, 260],
24 "drawsContent": true
25 }
26 ]
27 }
28 ]
29 }
30 ]
31 }
32 CASE 2, The original composited layer is no longer composited, which then also r emoves all squashing layers. The important point is that there should be an appr opriate repaint to the root GraphicsLayer:
33 {
34 "bounds": [800, 600],
35 "children": [
36 {
37 "bounds": [800, 600],
38 "contentsOpaque": true,
39 "drawsContent": true,
40 "repaintRects": [
41 [300, 300, 100, 100],
42 [220, 220, 100, 100],
43 [140, 140, 100, 100],
44 [60, 60, 100, 100],
45 [60, 60, 100, 100]
46 ]
47 }
48 ]
49 }
50
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698