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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt

Issue 14120003: Move LayoutTests from platform/chromium/... to generic location (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 7 years, 8 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 | Annotate | Revision Log
OLDNEW
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: [blocked] The page at about:blank displayed insecure content fr om http://127.0.0.1:8080/security/mixedContent/resources/boring.html. 7 CONSOLE MESSAGE: [blocked] The page at about:blank displayed insecure content fr om http://127.0.0.1:8080/security/mixedContent/resources/boring.html.
8 8
9 frame "<!--framePath //<!--frame0-->-->" - didFailProvisionalLoadWithError 9 frame "<!--framePath //<!--frame0-->-->" - didFailProvisionalLoadWithError
10 main frame - didFinishDocumentLoadForFrame 10 main frame - didFinishDocumentLoadForFrame
11 main frame - didHandleOnloadEventsForFrame 11 main frame - didHandleOnloadEventsForFrame
12 main frame - didFinishLoadForFrame 12 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. 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.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698