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

Side by Side Diff: LayoutTests/compositing/overlap-map-stack-crash.html

Issue 898783003: Move rendering/RenderLayer* to layout/ (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 5 years, 10 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
1 <!DOCTYPE html> 1 <!DOCTYPE html>
2 <html> 2 <html>
3 <head> 3 <head>
4 4
5 <style> 5 <style>
6 #container { 6 #container {
7 position: absolute; 7 position: absolute;
8 z-index: 0; 8 z-index: 0;
9 top: 50px; 9 top: 50px;
10 left: 50px; 10 left: 50px;
(...skipping 61 matching lines...) Expand 10 before | Expand all | Expand 10 after
72 Crash after hitting below bottom of overlap stack: https://code.google.com/p/chr omium/issues/detail?id=285979 72 Crash after hitting below bottom of overlap stack: https://code.google.com/p/chr omium/issues/detail?id=285979
73 73
74 The crashing scenario happened as follows: 74 The crashing scenario happened as follows:
75 75
76 - force-compositing-mode is disabled. As a result, compositing mode is 76 - force-compositing-mode is disabled. As a result, compositing mode is
77 disabled until a compositing trigger. 77 disabled until a compositing trigger.
78 78
79 - overflow-scroll as the compositing trigger, because it does not enable 79 - overflow-scroll as the compositing trigger, because it does not enable
80 compositing mode before computeCompositingRequirements. Other triggers 80 compositing mode before computeCompositingRequirements. Other triggers
81 happen during CompositedLayerMapping incremental update entry points. 81 happen during CompositedLayerMapping incremental update entry points.
82 (Note: CompositedLayerMapping was formerly known as RenderLayerBacking.) 82 (Note: CompositedLayerMapping was formerly known as LayerBacking.)
83 83
84 - The above two requirements are necessary to create the scenario where 84 - The above two requirements are necessary to create the scenario where
85 the root layer does not create an overlap context. 85 the root layer does not create an overlap context.
86 86
87 - The overflow-scroll element has a negative z-index which causes the 87 - The overflow-scroll element has a negative z-index which causes the
88 parent layer to be composited, too. 88 parent layer to be composited, too.
89 89
90 - As a result, subsequent children layers need to add themselves to the 90 - As a result, subsequent children layers need to add themselves to the
91 overlap map, even if they are not composited. 91 overlap map, even if they are not composited.
92 92
93 - The problem, however, is that we never created an overlap context for 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 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 95 themselves to the overlap, they try to access below the bottom of the
96 stack, and crash. 96 stack, and crash.
97 </pre> 97 </pre>
98 98
99 </body> 99 </body>
100 100
101 </html> 101 </html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698