third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-allowed-expected.txt - Issue 2278303002: Remove the allow-displaying-mixed-content setting from Blink.

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: third_party/WebKit/LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-allowed-expected.txt

Issue 2278303002: Remove the allow-displaying-mixed-content setting from Blink. (Closed)

Patch Set: Fixed missign deprecated preference registration. Created 4 years, 3 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 9: Mixed Content: The page at 'https://127.0.0.1:8443/secu rity/mixedContent/resources/frame-with-insecure-image.html' was loaded over HTTP S, but requested an insecure image 'http://example.test:8080/security/resources/ compass.jpg'. This content should also be served over HTTPS.	1 CONSOLE WARNING: line 9: Mixed Content: The page at 'https://127.0.0.1:8443/secu rity/mixedContent/resources/frame-with-insecure-image.html' was loaded over HTTP S, but requested an insecure image 'http://example.test:8080/security/resources/ compass.jpg'. This content should also be served over HTTPS.

2 This test opens a window that loads an insecure image. We should trigger a mixed content callback even though we've set the preference to block this, because we 've overriden the preference via a web permission client callback.	2 This test opens a window that loads an insecure image. We should trigger a mixed content callback because passive mixed content is allowed by default.

OLD	NEW