Index: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt |
index 462a75ba868c116122e6f2f0d9a9209fe2fe0f18..96c6bfd70e15ddc8af08c37d18b59a40c3e433c7 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-expected.txt |
@@ -1,3 +1,3 @@ |
-CONSOLE MESSAGE: line 9: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-iframe.html displayed insecure content from http://127.0.0.1:8080/security/mixedContent/resources/boring.html. |
+CONSOLE MESSAGE: line 9: [blocked] The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-iframe.html ran insecure content from http://127.0.0.1:8080/security/mixedContent/resources/boring.html. |
This test opens a window that loads an insecure iframe. We should not trigger a mixed content callback even though the main frame in the window is HTTPS and is displaying insecure content, because we've set the preference to block this. |