Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947) from Lauro Moraes on 2018-08-06 (public-webapps-github@w3.org from August 2018)

From: Lauro Moraes <notifications@github.com>
Date: Mon, 06 Aug 2018 11:57:58 -0700
To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/ServiceWorker/issues/947/410816076@github.com>

Hello everyone, I had already moved on to a quick reading on this issue some time ago.

Today testing the APIs available on the global object of a ServiceWorker I was surprised to find WebSocket running on Chrome.

I remember just coming to this discussion some time ago because trying to instantiate a socket in ServiceWorker would return an error.

Soon I ran to see if there were any changes that I had not noticed but it seems to me that there were no changes.

I searched for some information before I decided to share here, if there were any notes about Chrome | Chromium or even bugs reported but I did not find anything.

So I do not really know if there were changes or if this could be an experimental feature or a bug.

* **Chrome Stable**: version 68.0.3440.84 (64 bit) Ubuntu 18.04.1 LTS
* **Nginx**: 1.14.0 (reverse proxy to Node)
* **Node**: 10.8.0

-- 
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-410816076

Received on Monday, 6 August 2018 18:58:27 UTC