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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-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
« no previous file with comments | « no previous file | LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-allowed-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-insecure-frame.html ran insecure content from http://127. 0.0.1:8080/security/mixedContent/resources/boring.html.
2
1 This test loads a secure iframe that loads an insecure iframe. We should *not* g et a mixed content callback becase the main frame is HTTP and the grandchild ifr ame doesn't contaminate the child iframe's security origin with mixed content. 3 This test loads a secure iframe that loads an insecure iframe. We should *not* g et a mixed content callback becase the main frame is HTTP and the grandchild ifr ame doesn't contaminate the child iframe's security origin with mixed content.
2 4
3 5
OLDNEW
« no previous file with comments | « no previous file | LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-allowed-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698