| OLD | NEW |
| 1 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/webso
cket/resources/expect-throw-on-construction.html' was loaded over HTTPS, but ran
insecure content from 'ws://127.0.0.1:8880/echo': this content should also be l
oaded over HTTPS. | 1 CONSOLE WARNING: The page at 'https://127.0.0.1:8443/security/mixedContent/webso
cket/resources/expect-throw-on-construction.html' was loaded over HTTPS, but ran
insecure content from 'ws://127.0.0.1:8880/echo': this content should also be l
oaded over HTTPS. |
| 2 | 2 |
| 3 CONSOLE WARNING: Connecting to a non-secure WebSocket server from a secure origi
n is deprecated. | 3 CONSOLE WARNING: Connecting to a non-secure WebSocket server from a secure origi
n is deprecated. |
| 4 This is a testharness.js-based test. | 4 This is a testharness.js-based test. |
| 5 FAIL Test that when a HTTPS window that creates an insecure WebSocket connection
is opened, the mixed content callback is triggered because the main frame in th
e window is HTTPS but is trying connecting to an insecure WebSocket server. asse
rt_equals: evt.data expected "DONE" but got "FAIL: No exception was thrown" | 5 FAIL Test that when a HTTPS window that creates an insecure WebSocket connection
is opened, the mixed content callback is triggered because the main frame in th
e window is HTTPS but is trying connecting to an insecure WebSocket server. asse
rt_equals: evt.data expected "DONE" but got "FAIL: No exception was thrown" |
| 6 Harness: the test ran to completion. | 6 Harness: the test ran to completion. |
| 7 | 7 |
| OLD | NEW |