Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+1/-2/💬21)
  1 issues created:
  - Redesign of "extract header list values" expected (by annevk)
    https://github.com/w3c/ServiceWorker/issues/1360 

  8 issues received 21 new comments:
  - #940 Is it possible to serve service workers from CDN/remote origin? (9 by annevk, jvanbec, malthejorgensen)
    https://github.com/w3c/ServiceWorker/issues/940 
  - #1355 Order of messages to clients in same unit of related browsing contexts unclear (3 by annevk, mattto, mkruisselbrink)
    https://github.com/w3c/ServiceWorker/issues/1355 
  - #1295 Confusion around new events after skipWaiting (3 by asakusuma, mattto)
    https://github.com/w3c/ServiceWorker/issues/1295 
  - #1336 No good way to beacon during activate (2 by asakusuma, mattto)
    https://github.com/w3c/ServiceWorker/issues/1336 
  - #1316 Is resultingClientId preserved over redirects? (1 by mattto)
    https://github.com/w3c/ServiceWorker/issues/1316 
  - #1319 importScripts() on ServiceWorkerGlobalScope (1 by mattto)
    https://github.com/w3c/ServiceWorker/issues/1319 
  - #1292 Formalizing a timeout API (1 by mattto)
    https://github.com/w3c/ServiceWorker/issues/1292 
  - #1301 Does ServiceWorkerContainer.onmessage also get ExtendableMessageEvent object? (1 by mattto)
    https://github.com/w3c/ServiceWorker/issues/1301 

  2 issues closed:
  - No good way to beacon during activate https://github.com/w3c/ServiceWorker/issues/1336 
  - Is resultingClientId preserved over redirects? https://github.com/w3c/ServiceWorker/issues/1316 




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