OLD | NEW |
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-->-->" - didHandleOnloadEventsForFrame | 5 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame |
| 6 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame |
6 main frame - didHandleOnloadEventsForFrame | 7 main frame - didHandleOnloadEventsForFrame |
7 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame | |
8 main frame - didFinishLoadForFrame | 8 main frame - didFinishLoadForFrame |
9 ALERT: PASS: scheduled postMessage() before hashchange triggered. | 9 ALERT: PASS: scheduled postMessage() before hashchange triggered. |
10 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame | 10 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame |
11 frame "<!--framePath //<!--frame0-->-->" - didReceiveTitle: | 11 frame "<!--framePath //<!--frame0-->-->" - didReceiveTitle: |
12 ALERT: PASS: hashchange triggered after postMessage(). | 12 ALERT: PASS: hashchange triggered after postMessage(). |
13 This tests that cross-origin fragment navigations are asynchronous. It does so b
y scheduling a postMessage before scheduling the navigation. If the navigation i
s 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). | 13 This tests that cross-origin fragment navigations are asynchronous. It does so b
y scheduling a postMessage before scheduling the navigation. If the navigation i
s 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). |
14 | 14 |
15 This test passes if the didChangeLocationWithinPageForFrame callback fires after
the postMessage alert() fires. | 15 This test passes if the didChangeLocationWithinPageForFrame callback fires after
the postMessage alert() fires. |
16 | 16 |
17 | 17 |
OLD | NEW |