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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked.html

Issue 726563004: MixedContentChecker should not log blocked preload requests (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: test Created 6 years, 1 month 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
« no previous file with comments | « no previous file | LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked-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 <html> 1 <html>
2 <body> 2 <body>
3 <script> 3 <script>
4 if (window.testRunner) { 4 if (window.testRunner) {
5 testRunner.waitUntilDone(); 5 testRunner.waitUntilDone();
6 testRunner.dumpAsText(); 6 testRunner.dumpAsText();
7 testRunner.setCanOpenWindows(); 7 testRunner.setCanOpenWindows();
8 testRunner.setCloseRemainingWindowsWhenComplete(true); 8 testRunner.setCloseRemainingWindowsWhenComplete(true);
9 testRunner.overridePreference("WebKitAllowDisplayingInsecureContent", false) ; 9 testRunner.overridePreference("WebKitAllowDisplayingInsecureContent", false) ;
10 } 10 }
11 11
12 window.addEventListener("message", function (e) { 12 window.addEventListener("message", function (e) {
13 if (window.testRunner) 13 if (window.testRunner)
14 testRunner.notifyDone(); 14 testRunner.notifyDone();
15 }, false); 15 }, false);
16 16
17 </script> 17 </script>
18 <p>This test opens a window that loads an insecure image. We should not 18 <p>This test opens a window that loads an insecure image. We should not
19 trigger a mixed content callback even though the main frame in the window 19 trigger a mixed content callback even though the main frame in the window
20 is HTTPS and is displaying insecure content, because we've set the preference 20 is HTTPS and is displaying insecure content, because we've set the preference
21 to block this.</p> 21 to block this.</p>
22 <script> 22 <script>
23 window.open("https://127.0.0.1:8443/security/mixedContent/resources/frame-with-i nsecure-image.html"); 23 window.open("https://127.0.0.1:8443/security/mixedContent/resources/frame-preloa ds-insecure-image.html");
24 </script> 24 </script>
25 </body> 25 </body>
26 </html> 26 </html>
OLDNEW
« no previous file with comments | « no previous file | LayoutTests/http/tests/security/mixedContent/preload-insecure-image-in-main-frame-blocked-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698