| OLD | NEW |
| 1 main frame - didStartProvisionalLoadForFrame | 1 main frame - didStartProvisionalLoadForFrame |
| 2 main frame - didFinishDocumentLoadForFrame | 2 main frame - didFinishDocumentLoadForFrame |
| 3 main frame - didHandleOnloadEventsForFrame | 3 main frame - didHandleOnloadEventsForFrame |
| 4 main frame - didFinishLoadForFrame | 4 main frame - didFinishLoadForFrame |
| 5 main frame - didCommitLoadForFrame | 5 main frame - didCommitLoadForFrame |
| 6 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame | 6 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame |
| 7 CONSOLE MESSAGE: line 9: [blocked] The page at https://127.0.0.1:8443/security/m
ixedContent/resources/frame-with-insecure-iframe.html ran insecure content from
http://127.0.0.1:8080/security/mixedContent/resources/boring.html. | 7 CONSOLE MESSAGE: line 9: The page at https://127.0.0.1:8443/security/mixedConten
t/resources/frame-with-insecure-iframe.html displayed insecure content from http
://127.0.0.1:8080/security/mixedContent/resources/boring.html. |
| 8 | 8 |
| 9 frame "<!--framePath //<!--frame0-->-->" - didFailProvisionalLoadWithError | 9 didDisplayInsecureContent |
| 10 main frame - didFinishDocumentLoadForFrame | 10 main frame - didFinishDocumentLoadForFrame |
| 11 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame |
| 12 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame |
| 13 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame |
| 11 main frame - didHandleOnloadEventsForFrame | 14 main frame - didHandleOnloadEventsForFrame |
| 15 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame |
| 12 main frame - didFinishLoadForFrame | 16 main frame - didFinishLoadForFrame |
| 13 This test opens a window that loads an insecure iframe. We should not trigger a
mixed content callback even though the main frame in the window is HTTPS and is
displaying insecure content, because we've set the preference to block this. | 17 This test opens a window that loads an insecure iframe. We should not trigger a
mixed content callback even though the main frame in the window is HTTPS and is
displaying insecure content, because we've set the preference to block this. |
| OLD | NEW |