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

Side by Side Diff: LayoutTests/compositing/drag-opacity-crash.html

Issue 214053003: Don't use stale compositing state in LocalFrame::nodeImage (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 6 years, 9 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
« no previous file with comments | « no previous file | LayoutTests/compositing/drag-opacity-crash-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 <!DOCTYPE HTML>
2 <html>
3 <style>
4 #crasher {
5 width: 200px;
6 height: 200px;
7 background-color: tomato;
8 }
9 </style>
10 Test for crbug.com/354373: This test passes if it does not crash.<br/>
11 <div id="crasher" draggable="true"></div>
12 <script>
13 internals.settings.setForceCompositingMode(true);
14
15 onload = function() {
16 document.getElementById('crasher').addEventListener('dragstart', functio n() {
17 this.style.opacity = '0.5';
18 });
19 eventSender.mouseMoveTo(75, 75);
20 eventSender.mouseDown();
21 eventSender.mouseMoveTo(500, 400);
22 eventSender.mouseUp();
23
24 if (window.testRunner)
25 testRunner.dumpAsText();
26 }
27 </script>
28 </html>
OLDNEW
« no previous file with comments | « no previous file | LayoutTests/compositing/drag-opacity-crash-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698