Move the mixed-content blocking checks from synchronous Init to asynchronous InitializeConnection in WebSocket.cpp. This aligns the behaviour with the standard specifications where mixed-content failures trigger asynchronous error rather than throwing a synchronous SecurityError during WebSocket construction Differential Revision: https://phabricator.services.mozilla.com/D308017
10 lines
305 B
INI
10 lines
305 B
INI
[mixed-content.https.any.worker.html]
|
|
expected:
|
|
if (os == "mac") and not debug: [OK, CRASH]
|
|
if os == "android": [OK, CRASH]
|
|
|
|
[mixed-content.https.any.serviceworker.html]
|
|
expected:
|
|
if (os == "win") and not debug and (processor == "x86"): [OK, TIMEOUT]
|
|
if (os == "win") and debug: CRASH
|