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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-script-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 CONSOLE MESSAGE: [blocked] The page at https://127.0.0.1:8443/security/mixedCont ent/resources/frame-with-insecure-script.html ran insecure content from http://1 27.0.0.1:8080/security/mixedContent/resources/script.js. 6 CONSOLE MESSAGE: [blocked] The page at https://127.0.0.1:8443/security/mixedCont ent/resources/frame-with-insecure-script.html ran insecure content from http://1 27.0.0.1:8080/security/mixedContent/resources/script.js.
7 7
8 main frame - didFinishDocumentLoadForFrame 8 main frame - didFinishDocumentLoadForFrame
9 main frame - didHandleOnloadEventsForFrame 9 main frame - didHandleOnloadEventsForFrame
10 main frame - didFinishLoadForFrame 10 main frame - didFinishLoadForFrame
11 This test opens a window that loads an insecure script. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is running insecure scripts, because we've set the preference to block this. 11 This test opens a window that loads an insecure script. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is running insecure scripts, because we've set the preference to block this.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698