- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2017 17:00:22 +0000
- To: public-webapps-github-weekly@w3.org
- Message-Id: <E1e1xtG-0007EC-7u@uranus.w3.org>
Issues ------ * w3c/ServiceWorker (+2/-0/💬6) 2 issues created: - resurrected service workers don't fire an activate event which may break expectations (by wanderview) https://github.com/w3c/ServiceWorker/issues/1204 - Mixed feelings about ServiceWorker for module loader (by Krinkle) https://github.com/w3c/ServiceWorker/issues/1203 2 issues received 6 new comments: - #1204 resurrected service workers don't fire an activate event which may break expectations (4 by n8schloss, NekR, wanderview) https://github.com/w3c/ServiceWorker/issues/1204 - #1195 Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (2 by vdjeric) https://github.com/w3c/ServiceWorker/issues/1195 Pull requests ------------- * w3c/ServiceWorker (+1/-0/💬4) 1 pull requests submitted: - reflect WG change [depends on another PR] (by ylafon) https://github.com/w3c/ServiceWorker/pull/1202 1 pull requests received 4 new comments: - #1202 reflect WG change [depends on another PR] (4 by jakearchibald, ylafon, jungkees) https://github.com/w3c/ServiceWorker/pull/1202 Repositories tracked by this digest: ----------------------------------- * https://github.com/w3c/ServiceWorker
Received on Tuesday, 10 October 2017 17:00:10 UTC