- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 14 Nov 2017 17:00:30 +0000
- To: public-webapps-github-weekly@w3.org
- Message-Id: <E1eEeZa-00033z-Ag@uranus.w3.org>
Issues
------
* w3c/ServiceWorker (+3/-2/💬36)
3 issues created:
- Provide a way to ask the waiting Service Worker to skip waiting from the outside (by dfabulich)
https://github.com/w3c/ServiceWorker/issues/1223
- Provide a one-line way to listen for a waiting Service Worker (by dfabulich)
https://github.com/w3c/ServiceWorker/issues/1222
- Should we specify behavior for using objects from detached contexts? (by mattto)
https://github.com/w3c/ServiceWorker/issues/1221
18 issues received 36 new comments:
- #1167 Proposal: FetchEvent.navigationLoadType (11 by annevk, jakearchibald, camillelamy, NekR, davidcblack)
https://github.com/w3c/ServiceWorker/issues/1167
- #204 _Update algorithm should unregister SW on 404 and 410 errors (3 by annevk, jakearchibald)
https://github.com/w3c/ServiceWorker/issues/204
- #1206 Create F2F agenda - 7 November 2017 (3 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1206
- #719 "no-cors" CSS SOP violation (3 by slightlyoff, jakearchibald)
https://github.com/w3c/ServiceWorker/issues/719
- #1221 Should we specify behavior for using objects from detached contexts? (2 by mattto, wanderview)
https://github.com/w3c/ServiceWorker/issues/1221
- #1191 What happens to the request body if the fetch isn't handled? (2 by annevk, jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1191
- #1216 Should we expose reserved clients? (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1216
- #1026 Consider mechanisms to bypass the service worker for things that we know won't be in it's cache (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1026
- #1123 WindowClient.navigate() behavior for reserved clients and in-flight navigations (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1123
- #452 Backpressure on fetch integrated with Streams (1 by xgqfrms-GitHub)
https://github.com/w3c/ServiceWorker/issues/452
- #745 Expose GeoLocation to workers (1 by MeritBased)
https://github.com/w3c/ServiceWorker/issues/745
- #1195 Proposal: Allow addEventListener/removeEventListener for 'fetch' to called at anytime (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1195
- #1200 is the browser required to start the ServiceWorker for postMessage() if there is no message event handler? (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1200
- #1091 consider Client behavior for windows where initial about:blank is replaced with a loaded document (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1091
- #1204 resurrected service workers don't fire an activate event which may break expectations (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1204
- #886 consider firing a "clientcontrolled" event on ServiceWorkerGlobalScope (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/886
- #1213 async waitUntil microtask issue (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1213
- #1189 Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/issues/1189
2 issues closed:
- Provide a way to ask the waiting Service Worker to skip waiting from the outside https://github.com/w3c/ServiceWorker/issues/1223
- _Update algorithm should unregister SW on 404 and 410 errors https://github.com/w3c/ServiceWorker/issues/204
Pull requests
-------------
* w3c/ServiceWorker (+1/-0/💬1)
1 pull requests submitted:
- Remove <link rel=serviceworker> (by sideshowbarker)
https://github.com/w3c/ServiceWorker/pull/1220
1 pull requests received 1 new comments:
- #1207 Remove foreign fetch (1 by jakearchibald)
https://github.com/w3c/ServiceWorker/pull/1207
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/ServiceWorker
Received on Tuesday, 14 November 2017 17:00:33 UTC