Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+3/-0/💬11)
  3 issues created:
  - Browsers should not consume the stream right away on ReadableStream responses with 'Content-Disposition: attachment' header. (by Khivar)
    https://github.com/w3c/ServiceWorker/issues/1398 
  - provide a way to execute work after browser has consumed a response (by wanderview)
    https://github.com/w3c/ServiceWorker/issues/1397 
  - spec should document Cache API HEIST mitigations (by wanderview)
    https://github.com/w3c/ServiceWorker/issues/1396 

  2 issues received 11 new comments:
  - #1397 provide a way to execute work after browser has consumed a response (10 by asakusuma, asutherland, jakearchibald, wanderview)
    https://github.com/w3c/ServiceWorker/issues/1397 
  - #1395 Is respondWith(fetch(event.request)) always the same as not calling respondWith()? (1 by asakusuma)
    https://github.com/w3c/ServiceWorker/issues/1395 




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