Weekly github digest (Service Worker WG specs)

Issues
------
* w3c/ServiceWorker (+1/-0/💬10)
  1 issues created:
  - should FetchEvent.request ever be a range request if we cannot verify if the underlying resource is the same? (by wanderview)
    https://github.com/w3c/ServiceWorker/issues/1201

  3 issues received 10 new comments:
  - #1201 should FetchEvent.request ever be a range request if we cannot verify if the underlying resource is the same? (7 by annevk, jakearchibald, wanderview)
    https://github.com/w3c/ServiceWorker/issues/1201
  - #1195 Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (2 by jakearchibald, bgirard)
    https://github.com/w3c/ServiceWorker/issues/1195
  - #1196 Issues with "Handle Functional Event" (1 by jungkees)
    https://github.com/w3c/ServiceWorker/issues/1196



Pull requests
-------------
* w3c/ServiceWorker (+0/-0/💬6)
  3 pull requests received 6 new comments:
  - #1178 Handing fetch termination (4 by annevk, jakearchibald)
    https://github.com/w3c/ServiceWorker/pull/1178
  - #1190 Remove incumbent/fetching record from Cache behavior (1 by jungkees)
    https://github.com/w3c/ServiceWorker/pull/1190
  - #1199 Making functional events simpler (1 by jungkees)
    https://github.com/w3c/ServiceWorker/pull/1199


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