Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+3/-2/💬14)
  3 issues created:
  - Should register() trigger byte-for-byte checking when WorkerType is updated? (by makotoshimazu)
    https://github.com/w3c/ServiceWorker/issues/1408 
  - Top-level await integration for ServiceWorkers running modules (by littledan)
    https://github.com/w3c/ServiceWorker/issues/1407 
  - New 'update via cache' value doesn't take effect in register algorithm. (by tingshao)
    https://github.com/w3c/ServiceWorker/issues/1406 

  4 issues received 14 new comments:
  - #1407 Top-level await integration for ServiceWorkers running modules (9 by jakearchibald, littledan, wanderview)
    https://github.com/w3c/ServiceWorker/issues/1407 
  - #1408 Should register() trigger byte-for-byte checking when WorkerType is updated? (2 by makotoshimazu, mattto)
    https://github.com/w3c/ServiceWorker/issues/1408 
  - #1406 New 'update via cache' value doesn't take effect in register algorithm. (2 by makotoshimazu, tingshao)
    https://github.com/w3c/ServiceWorker/issues/1406 
  - #1399 Pass credentials on navigator.serviceWorker.register("/service_worker.js"); (1 by SystemR)
    https://github.com/w3c/ServiceWorker/issues/1399 

  2 issues closed:
  - New 'update via cache' value doesn't take effect in register algorithm. https://github.com/w3c/ServiceWorker/issues/1406 
  - Pass credentials on navigator.serviceWorker.register("/service_worker.js"); https://github.com/w3c/ServiceWorker/issues/1399 




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