Index: LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
index aa79a01fac0588584eae6b3d8fa0bb18322187a8..8b8654f288260b027d69e82ec79afef59e453306 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-expected.txt |
@@ -1,3 +1,3 @@ |
-CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-frame.html displayed insecure content from http://127.0.0.1:8080/security/mixedContent/resources/boring.html. |
+CONSOLE MESSAGE: line 8: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-frame.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 trigger a mixed content callback because the main frame in the window is HTTPS but is running insecure content. |