Index: LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
diff --git a/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt b/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
index 3e57ec31a8eb2c13217281c4e706c38c91bad37e..06b8198e3566e0075c93b84beb1e93095dbaf114 100644 |
--- a/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
+++ b/LayoutTests/http/tests/security/mixedContent/insecure-css-in-main-frame-expected.txt |
@@ -1,3 +1,3 @@ |
-CONSOLE MESSAGE: line 4: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css': this content should also be loaded over HTTPS. |
+CONSOLE WARNING: line 4: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/security/mixedContent/resources/style.css': this content should also be loaded over HTTPS. |
This test opens a window that loads an insecure style sheet. We should trigger a mixed content callback because the main frame in the window is HTTPS but is running insecure content. |