OLD | NEW |
| (Empty) |
1 <!DOCTYPE html> | |
2 <html> | |
3 | |
4 <head> | |
5 <style> | |
6 | |
7 .compositedBehind { | |
8 width: 500px; | |
9 height: 500px; | |
10 transform: translatez(0); | |
11 background-color: cyan; | |
12 } | |
13 | |
14 .containerOverlapsComposited { | |
15 position: absolute; | |
16 z-index: 2; /* Creates a stacking context so that the fixed-pos layer is conta
ined instead of a sibling */ | |
17 top: 20px; | |
18 left: 20px; | |
19 width: 100px; | |
20 height: 30000px; | |
21 background-color: green; | |
22 } | |
23 | |
24 .absolute { | |
25 position: absolute; | |
26 top: 145px; | |
27 left: 45px; | |
28 background-color: lime; | |
29 width: 50px; | |
30 height: 50px; | |
31 z-index: 3; | |
32 } | |
33 | |
34 </style> | |
35 | |
36 <script> | |
37 if (window.internals) { | |
38 /* Note carefully, compositing for fixed position is _disabled_ here
*/ | |
39 internals.settings.setPreferCompositingToLCDTextEnabled(false); | |
40 } | |
41 | |
42 onload = function() { | |
43 window.scrollTo(0, 100); | |
44 } | |
45 </script> | |
46 | |
47 </head> | |
48 | |
49 | |
50 | |
51 <body> | |
52 <!-- | |
53 Among other duplicate bugs: https://code.google.com/p/chromium/issues/det
ail?id=128375 | |
54 A non-composited fixed-position element can get grouped into a composited
container. | |
55 In this case, repaint invalidations were incorrectly going to the LayoutV
iew instead | |
56 of the composited container. The incorrect result was that the fixed-pos
ition element | |
57 never repainted, and it appeared to scroll along with the composited cont
ainer. | |
58 --> | |
59 <div class="compositedBehind"> </div> | |
60 | |
61 <div class="containerOverlapsComposited"></div> | |
62 | |
63 <div class="absolute"></div> | |
64 </body> | |
65 | |
66 </html> | |
OLD | NEW |