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

Side by Side Diff: LayoutTests/http/tests/security/mixedContent/insecure-image-in-main-frame-allowed-expected.txt

Issue 200923002: Post a microtask to load <img> elements. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: fix last test failure Created 6 years, 7 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 unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 CONSOLE WARNING: line 1: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-image.html' was loaded over HTTPS, but displaye d insecure content from 'http://127.0.0.1:8080/security/resources/compass.jpg': this content should also be loaded over HTTPS. 1 CONSOLE WARNING: line 7: The page at 'https://127.0.0.1:8443/security/mixedConte nt/resources/frame-with-insecure-image.html' was loaded over HTTPS, but displaye d insecure content from 'http://127.0.0.1:8080/security/resources/compass.jpg': this content should also be loaded over HTTPS.
2 2
3 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. 3 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.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698