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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/navigation/same-origin-fragment-navigation-is-sync-expected.txt

Issue 2943523002: Fire start/stop based on Frame::IsLoading for same document navigations (Closed)
Patch Set: Fire start/stop based on IsLoading Created 3 years, 6 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
OLDNEW
1 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame 1 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame
2 main frame - didFinishDocumentLoadForFrame 2 main frame - didFinishDocumentLoadForFrame
3 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame 3 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame
4 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame 4 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame
5 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame 5 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame
6 frame "<!--framePath //<!--frame0-->-->" - didReceiveTitle:
7 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame 6 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame
8 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame 7 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame
9 main frame - didHandleOnloadEventsForFrame 8 main frame - didHandleOnloadEventsForFrame
10 main frame - didFinishLoadForFrame 9 main frame - didFinishLoadForFrame
11 ALERT: PASS: scheduled postMessage() before hashchange triggered. 10 ALERT: PASS: scheduled postMessage() before hashchange triggered.
12 ALERT: PASS: hashchange triggered after postMessage(). 11 ALERT: PASS: hashchange triggered after postMessage().
13 This tests that same-origin fragment navigations are synchronous. It does so by scheduling a postMessage before scheduling the navigation. If the navigation is synchronous, the frame load callback for the load's commit will happen before th e message is handled. This isn't as flaky as it sounds, though it does rely on t his postMessage behavior (which seems reasonable to do). 12 This tests that same-origin fragment navigations are synchronous. It does so by scheduling a postMessage before scheduling the navigation. If the navigation is synchronous, the frame load callback for the load's commit will happen before th e message is handled. This isn't as flaky as it sounds, though it does rely on t his postMessage behavior (which seems reasonable to do).
14 13
15 This test passes if the didChangeLocationWithinPageForFrame callback fires befor e the postMessage alert() fires. 14 This test passes if the didChangeLocationWithinPageForFrame callback fires befor e the postMessage alert() fires.
16 15
17 16
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698