LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt - Issue 18104009: Mixed content iframe checks should use top

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

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

Issue 18104009: Mixed content iframe checks should use top (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Drop back to canDisplay 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 side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-allowed-expected.txt ('k') | LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

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

diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt

index 9010e2e1e0ee6e7c4533081f74119b8450f13be5..f3ccb67f0f75098205a4f189dd1877e4f3b7c4df 100644

--- a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt

+++ b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt

@@ -4,10 +4,14 @@ main frame - didHandleOnloadEventsForFrame

main frame - didFinishLoadForFrame

main frame - didCommitLoadForFrame

frame "-->" - didStartProvisionalLoadForFrame

-CONSOLE MESSAGE: line 9: [blocked] The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-iframe.html ran insecure content from http://127.0.0.1:8080/security/mixedContent/resources/boring.html.

+CONSOLE MESSAGE: line 9: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-iframe.html displayed insecure content from http://127.0.0.1:8080/security/mixedContent/resources/boring.html.

-frame "-->" - didFailProvisionalLoadWithError

+didDisplayInsecureContent

main frame - didFinishDocumentLoadForFrame

+frame "-->" - didCommitLoadForFrame

+frame "-->" - didFinishDocumentLoadForFrame

+frame "-->" - didHandleOnloadEventsForFrame

main frame - didHandleOnloadEventsForFrame

+frame "-->" - didFinishLoadForFrame

main frame - didFinishLoadForFrame

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.