Index: third_party/WebKit/LayoutTests/http/tests/navigation/cross-origin-fragment-navigation-is-async-expected.txt |
diff --git a/third_party/WebKit/LayoutTests/http/tests/navigation/cross-origin-fragment-navigation-is-async-expected.txt b/third_party/WebKit/LayoutTests/http/tests/navigation/cross-origin-fragment-navigation-is-async-expected.txt |
index 47c8edbc3fc70f14e5a6db67c1b6f8d7e0ed1694..f5ba24a4db157b000d702c29faba43e31502a5fa 100644 |
--- a/third_party/WebKit/LayoutTests/http/tests/navigation/cross-origin-fragment-navigation-is-async-expected.txt |
+++ b/third_party/WebKit/LayoutTests/http/tests/navigation/cross-origin-fragment-navigation-is-async-expected.txt |
@@ -8,7 +8,6 @@ main frame - didHandleOnloadEventsForFrame |
main frame - didFinishLoadForFrame |
ALERT: PASS: scheduled postMessage() before hashchange triggered. |
frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame |
-frame "<!--framePath //<!--frame0-->-->" - didReceiveTitle: |
ALERT: PASS: hashchange triggered after postMessage(). |
This tests that cross-origin fragment navigations are asynchronous. 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 the message is handled. This isn't as flaky as it sounds, though it does rely on this postMessage behavior (which seems reasonable to do). |