http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe.html is flaky: Diff: --- /Volumes/Data/worker/debug-wk2-tests/build/OpenSource/layout-test-results/http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe-expected.txt +++ /Volumes/Data/worker/debug-wk2-tests/build/OpenSource/layout-test-results/http/tests/security/mixedContent/websocket/insecure-websocket-in-iframe-actual.txt @@ -2,7 +2,6 @@ CONSOLE MESSAGE: WebSocket connection failed. CONSOLE MESSAGE: WebSocket connection failed: WebSocket is closed before the connection is established. -CONSOLE MESSAGE: WebSocket closed. This test loads an iframe that creates an insecure WebSocket connection. We should block the connection and trigger a mixed content callback because the main frame is HTTPS, but the data sent over the socket could be recorded or controlled by an attacker.
<rdar://84997169>
Created attachment 443458 [details] Patch
*** This bug has been marked as a duplicate of bug 232810 ***