LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-expected.txt - Issue 26770004: Add console message levels to test expectation output.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

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

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

Issue 26770004: Add console message levels to test expectation output. (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Tests. Created 7 years, 2 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:

OLD	NEW
1 CONSOLE MESSAGE: line 8: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-frame.html' was loaded over HTTPS, but ran inse cure content from 'http://127.0.0.1:8080/security/mixedContent/resources/boring. html': this content should also be loaded over HTTPS.	1 CONSOLE WARNING: line 8: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-frame.html' was loaded over HTTPS, but ran inse cure content from 'http://127.0.0.1:8080/security/mixedContent/resources/boring. html': this content should also be loaded over HTTPS.

2	2

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.	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.

4	4

5	5

OLD	NEW