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

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

Issue 26770004: Add console message levels to test expectation output. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Tests. Created 7 years, 2 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 MESSAGE: The page at 'https://127.0.0.1:8443/security/mixedContent/resou rces/frame-with-insecure-audio-video.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/resources/test.mp4': this content s hould also be loaded over HTTPS. 1 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resou rces/frame-with-insecure-audio-video.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/resources/test.mp4': this content s hould also be loaded over HTTPS.
2 2
3 CONSOLE MESSAGE: The page at 'https://127.0.0.1:8443/security/mixedContent/resou rces/frame-with-insecure-audio-video.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/resources/test.mp4': this content s hould also be loaded over HTTPS. 3 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/resou rces/frame-with-insecure-audio-video.html' was loaded over HTTPS, but displayed insecure content from 'http://127.0.0.1:8080/resources/test.mp4': this content s hould also be loaded over HTTPS.
4 4
5 This test opens a window that loads insecure HTML5 audio and video. We should tr igger a mixed content callback because the main frame in the window is HTTPS but is displaying insecure content. 5 This test opens a window that loads insecure HTML5 audio and video. We should tr igger a mixed content callback because the main frame in the window is HTTPS but is displaying insecure content.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698