Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+2/-2/💬19)
  2 issues created:
  - Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (by mattto)
    https://github.com/w3c/ServiceWorker/issues/1395 
  - Can respondWith() be called from a microtask? (by mattto)
    https://github.com/w3c/ServiceWorker/issues/1394 

  5 issues received 19 new comments:
  - #1213 async waitUntil microtask issue (10 by annevk, mattto, asutherland, wanderview)
    https://github.com/w3c/ServiceWorker/issues/1213 
  - #1394 Can respondWith() be called from a microtask? (5 by mattto, wanderview)
    https://github.com/w3c/ServiceWorker/issues/1394 
  - #707 Add cookie accessor/setter methods? (2 by NekR, wanderview)
    https://github.com/w3c/ServiceWorker/issues/707 [apr-2017-f2f] 
  - #1392 Fully inline (.js + json manifest) service worker (1 by mattto)
    https://github.com/w3c/ServiceWorker/issues/1392 
  - #1395 Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (1 by annevk)
    https://github.com/w3c/ServiceWorker/issues/1395 

  2 issues closed:
  - async waitUntil microtask issue https://github.com/w3c/ServiceWorker/issues/1213 
  - Can respondWith() be called from a microtask? https://github.com/w3c/ServiceWorker/issues/1394 



Pull requests
-------------
* w3c/ServiceWorker (+0/-0/💬3)
  2 pull requests received 3 new comments:
  - #1242 Add CR Plan for V1 (2 by jungkees, mattto)
    https://github.com/w3c/ServiceWorker/pull/1242 
  - #1175 Fix the perform the fetch steps in Update algorithm (1 by mattto)
    https://github.com/w3c/ServiceWorker/pull/1175 


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

Received on Tuesday, 19 March 2019 17:01:59 UTC