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

Side by Side Diff: LayoutTests/fast/loader/stateobjects/state-attribute-only-one-deserialization.html

Issue 54473004: Make js-test-post a noop. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: add mac NeedsRebaselines Created 7 years, 1 month 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 <script src="../../js/resources/js-test-pre.js"></script> 4 <script src="../../js/resources/js-test-pre.js"></script>
5 </head/> 5 </head/>
6 <body> 6 <body>
7 <script> 7 <script>
8 description("Make sure the same deserialization of the state object is used every time (both in the history object and popstate events)."); 8 description("Make sure the same deserialization of the state object is used every time (both in the history object and popstate events).");
9 9
10 window.jsTestIsAsync = true; 10 window.jsTestIsAsync = true;
(...skipping 29 matching lines...) Expand all
40 window.onpopstate = function(e) { 40 window.onpopstate = function(e) {
41 debug("\nInside popstate event\n"); 41 debug("\nInside popstate event\n");
42 popStateEvent = e; 42 popStateEvent = e;
43 // Our stored reference to stateObject will not match the current state object, as it is a structured clone of the history item's state object. 43 // Our stored reference to stateObject will not match the current state object, as it is a structured clone of the history item's state object.
44 shouldBeTrue("history.state !== stateObject"); 44 shouldBeTrue("history.state !== stateObject");
45 // Our stored reference to stateObject will not match the state object i n this pop state event, as it is the same as history.state which is a structured clone of the history item's state object. 45 // Our stored reference to stateObject will not match the state object i n this pop state event, as it is the same as history.state which is a structured clone of the history item's state object.
46 shouldBeTrue("popStateEvent.state !== stateObject"); 46 shouldBeTrue("popStateEvent.state !== stateObject");
47 // The event's state object and the current state object should match. 47 // The event's state object and the current state object should match.
48 shouldBeTrue("popStateEvent.state === history.state"); 48 shouldBeTrue("popStateEvent.state === history.state");
49 49
50 var s = document.createElement("script");
51 s.src = "../../js/resources/js-test-post.js";
52 document.body.appendChild(s);
53 setTimeout(finishJSTest, 0); 50 setTimeout(finishJSTest, 0);
54 } 51 }
55 52
56 // Now let's go back to our original history entry which has a state object that we've stored a reference to already. 53 // Now let's go back to our original history entry which has a state object that we've stored a reference to already.
57 // This will fire our popstate event handler above. 54 // This will fire our popstate event handler above.
58 history.back(); 55 history.back();
59 </script> 56 </script>
60 </body> 57 </body>
61 </html> 58 </html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698