| 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-->-->" - didCommitLoadForFrame | 5 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame |
| 6 frame "<!--framePath //<!--frame0-->-->" - didReceiveTitle: | 6 frame "<!--framePath //<!--frame0-->-->" - didReceiveTitle: |
| 7 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame | 7 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame |
| 8 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame |
| 8 main frame - didHandleOnloadEventsForFrame | 9 main frame - didHandleOnloadEventsForFrame |
| 9 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame | |
| 10 main frame - didFinishLoadForFrame | 10 main frame - didFinishLoadForFrame |
| 11 ALERT: PASS: scheduled postMessage() before hashchange triggered. | 11 ALERT: PASS: scheduled postMessage() before hashchange triggered. |
| 12 ALERT: PASS: hashchange triggered after postMessage(). | 12 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). | 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). |
| 14 | 14 |
| 15 This test passes if the didChangeLocationWithinPageForFrame callback fires befor
e the postMessage alert() fires. | 15 This test passes if the didChangeLocationWithinPageForFrame callback fires befor
e the postMessage alert() fires. |
| 16 | 16 |
| 17 | 17 |
| OLD | NEW |