Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+0/-3/💬8)
  6 issues received 8 new comments:
  - #1480 Service worker expiration (3 by TomPradat, jakearchibald)
    https://github.com/w3c/ServiceWorker/issues/1480 
  - #1366 Why does spec set redirect's mode to error ? (1 by jakearchibald)
    https://github.com/w3c/ServiceWorker/issues/1366 
  - #1200 is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? (1 by mattto)
    https://github.com/w3c/ServiceWorker/issues/1200 [decided] 
  - #1004 Behavior of the onfetch setter regarding no-fetch service workers (1 by jungkees)
    https://github.com/w3c/ServiceWorker/issues/1004 [apr-2017-f2f-v1] [bug] 
  - #339 Is fetch() before or after Content-Encoding (1 by sheerun)
    https://github.com/w3c/ServiceWorker/issues/339 [fetch] [no impact (blink)] 
  - #204 _Update algorithm should unregister SW on 404 and 410 errors (1 by TomPradat)
    https://github.com/w3c/ServiceWorker/issues/204 [no impact (blink)] [wontfix] 

  3 issues closed:
  - Behavior of the onfetch setter regarding no-fetch service workers https://github.com/w3c/ServiceWorker/issues/1004 [apr-2017-f2f-v1] [bug] 
  - Why does spec set redirect's mode to error ? https://github.com/w3c/ServiceWorker/issues/1366 
  - Service worker expiration https://github.com/w3c/ServiceWorker/issues/1480 




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/ServiceWorker