LayoutTests/http/tests/security/mixedContent/insecure-css-in-iframe-expected.txt - Issue 302063002: Always preload all tokens before parsing

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-css-in-iframe-expected.txt

Issue 302063002: Always preload all tokens before parsing (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Fix another flaky tests Created 6 years, 6 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 WARNING: line 1: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecu re content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css ': this content should also be loaded over HTTPS.

	2

1 CONSOLE WARNING: line 4: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecu re content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css ': this content should also be loaded over HTTPS.	3 CONSOLE WARNING: line 4: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecu re content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css ': this content should also be loaded over HTTPS.

2	4

3 This test loads a secure iframe that loads an insecure style sheet. We should tr igger a mixed content callback because an active network attacker can use CSS3 t o breach the confidentiality of the HTTPS security origin.	5 This test loads a secure iframe that loads an insecure style sheet. We should tr igger a mixed content callback because an active network attacker can use CSS3 t o breach the confidentiality of the HTTPS security origin.

4	6

5	7

OLD	NEW