CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css-resources.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/css/resources/cors-ahem.php': this content should also be loaded over HTTPS.

CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css-resources.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/resources/square20.png': this content should also be loaded over HTTPS.

CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css-resources.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/css/resources/cors-ahem.php': this content should also be loaded over HTTPS.

This test opens a window that loads a style sheet which fetches an insecure background image and an insecure web font. We should trigger a mixed content callback because the main frame in the window is HTTPS but is running insecure content.

CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css-resources.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/css/resources/cors-ahem.php': this content should also be loaded over HTTPS.

CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css-resources.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/resources/square20.png': this content should also be loaded over HTTPS.

CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-css-resources.html' was loaded over HTTPS, but ran insecure content from 'http://127.0.0.1:8080/css/resources/cors-ahem.php': this content should also be loaded over HTTPS.

This test opens a window that loads a style sheet which fetches an insecure background image and an insecure web font. We should trigger a mixed content callback because the main frame in the window is HTTPS but is running insecure content.

Fix the insecure-css-resources.html layout test.
Fix the insecure-css-resources.html layout test.

CSS content is considered as active content, and therefore "runs" instead
of "displays". Change this in the test expectations.

TBR=dcheng@chromium.org, bashi@chromium.org
NOTRY=true
BUG=377864

Review URL: https://codereview.chromium.org/317173002

git-svn-id: bf5cd6ccde378db821296732a091cfbcf5285fbd@175570 bbb929c8-8fbe-4397-9dbb-9b2b20218538
