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

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

Issue 19551006: Re-instantiate the mixed iframe block for M30. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 7 years, 5 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 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. 1 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.
2 2
3 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. 3 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