Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+6/-2/💬8)
  6 issues created:
  - Response's cache state is back (by annevk)
    https://github.com/w3c/ServiceWorker/issues/1308 
  - Service-Worker-Allowed can be cross-origin to the script URL. (by mattto)
    https://github.com/w3c/ServiceWorker/issues/1307 
  - Correct link to nightly version (by Malvoz)
    https://github.com/w3c/ServiceWorker/issues/1306 
  - how can unregister()'s same-origin check ever fail? (by wanderview)
    https://github.com/w3c/ServiceWorker/issues/1305 
  - spec says `update()` should resolve to a registration, but browsers resolve to undefined (by wanderview)
    https://github.com/w3c/ServiceWorker/issues/1304 
  - Create F2F agenda - 25 October 2018 (by jatindersmann)
    https://github.com/w3c/ServiceWorker/issues/1303 

  5 issues received 8 new comments:
  - #755 consult document CSP in Register algorithm (3 by annevk, wanderview)
    https://github.com/w3c/ServiceWorker/issues/755 
  - #1304 spec says `update()` should resolve to a registration, but browsers do different things (2 by wanderview)
    https://github.com/w3c/ServiceWorker/issues/1304 
  - #980 postMessage keeps service workers alive indefinitely (1 by valioDOTch)
    https://github.com/w3c/ServiceWorker/issues/980 
  - #1269 windowClients state change events - loaded/unloaded (1 by romandev)
    https://github.com/w3c/ServiceWorker/issues/1269 
  - #719 "no-cors" CSS SOP violation (1 by yoavweiss)
    https://github.com/w3c/ServiceWorker/issues/719 [apr-2017-f2f-v1] 

  2 issues closed:
  - Correct link to nightly version https://github.com/w3c/ServiceWorker/issues/1306 
  - spec says `update()` should resolve to a registration, but browsers do different things https://github.com/w3c/ServiceWorker/issues/1304 




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