- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 08 Jan 2019 17:00:55 +0000
- To: public-webapps-github-weekly@w3.org
- Message-Id: <E1ggukJ-0006z9-V4@uranus.w3.org>
Issues ------ * w3c/ServiceWorker (+1/-1/💬44) 1 issues created: - Add registeringClientId to the ServiceWorker object (by philipwalton) https://github.com/w3c/ServiceWorker/issues/1379 4 issues received 44 new comments: - #1373 Declarative routing (39 by hewholived, tomayac, domenic, AmeliaBR, annevk, aaronsn, WORMSS, wanderview, richardkazuomiller, jakearchibald, yoavweiss, shortercode, jeffposnick, nhoizey, Pajn) https://github.com/w3c/ServiceWorker/issues/1373 - #1378 Can service workers mess with POST variables? (2 by annevk) https://github.com/w3c/ServiceWorker/issues/1378 - #719 "no-cors" CSS SOP violation (2 by aliams, wanderview) https://github.com/w3c/ServiceWorker/issues/719 [apr-2017-f2f-v1] - #1345 Consider exposing Page Lifecycle state to service-worker (1 by jsaterfiel) https://github.com/w3c/ServiceWorker/issues/1345 1 issues closed: - Can service workers mess with POST variables? https://github.com/w3c/ServiceWorker/issues/1378 Repositories tracked by this digest: ----------------------------------- * https://github.com/w3c/ServiceWorker
Received on Tuesday, 8 January 2019 17:00:57 UTC