13 background-color: gray;
16 #compositedNegZIndex {
21 background-color: blue;
36 background-color: lime;
46 if (window
.internals
) {
47 window
.internals
.settings
.setPreferCompositingToLCDTextEnabled(true);
51 if (!window
.internals
)
52 document
.getElementById("explanation").style
.display
= "block";
54 if (window
.testRunner
)
55 testRunner
.dumpAsText();
58 window
.addEventListener("load", doTest
, false);
65 <div id=
"compositedNegZIndex">
68 <div id=
"innocentNegZIndex"> </div>
71 <pre id=
"explanation" style=
"display:none;">
72 Crash after hitting below bottom of overlap stack: https://code.google.com/p/chromium/issues/detail?id=
285979
74 The crashing scenario happened as follows:
76 - force-compositing-mode is disabled. As a result, compositing mode is
77 disabled until a compositing trigger.
79 - overflow-scroll as the compositing trigger, because it does not enable
80 compositing mode before computeCompositingRequirements. Other triggers
81 happen during CompositedLayerMapping incremental update entry points.
82 (Note: CompositedLayerMapping was formerly known as LayerBacking.)
84 - The above two requirements are necessary to create the scenario where
85 the root layer does not create an overlap context.
87 - The overflow-scroll element has a negative z-index which causes the
88 parent layer to be composited, too.
90 - As a result, subsequent children layers need to add themselves to the
91 overlap map, even if they are not composited.
93 - The problem, however, is that we never created an overlap context for
94 these negative z-index non-composited layers. When the layers try to add
95 themselves to the overlap, they try to access below the bottom of the