You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi we can't test anymore if the websocket is supported and not blocked due to used services to estabilish wss connection (wss: //echo.websocket.org: 443 /) since is down, instead we could use wss://echo.websocket.events/.ws. (I tried it and it works)
Furthermore we can add some improvements too. Now we can't differentiate between an error and a success connection in the provided callback to checkWebSocketsSupport fn unless we verify isWebSocketsBlocked variable that is not really intuitive in my opinion.
The text was updated successfully, but these errors were encountered:
Hi we can't test anymore if the websocket is supported and not blocked due to used services to estabilish wss connection (wss: //echo.websocket.org: 443 /) since is down, instead we could use wss://echo.websocket.events/.ws. (I tried it and it works)
Furthermore we can add some improvements too. Now we can't differentiate between an error and a success connection in the provided callback to checkWebSocketsSupport fn unless we verify isWebSocketsBlocked variable that is not really intuitive in my opinion.
The text was updated successfully, but these errors were encountered: