Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947)

Hi @kael 

I followed the threaded thread but, I did not find exactly where in that version (path, release) Chrome came to support WebSocket within ServiceWorker. There are some versions back I could not stand.

I hoped that:

* when updating the page (user press **F5** or front `window.location.reload()`) or browsing there is another page the socket connection was closed

This is not happening and the connection continues to be persisted. There may be some scenario that this is helpful, but I believe this is not the standard.

Just out of curiosity: the socket connection started in the ServiceWorker is not shown in the `Network > WS`. As in Developer Tools, the socket does not lose the connection even after simulating the offline state.

I'm not using the **ws** module, I'm using the native API in frontend and **uws** in the backend.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/947#issuecomment-411146303