- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 01 Oct 2019 17:01:13 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1iFLWT-0001eN-6N@uranus.w3.org>
Issues
------
* w3c/resource-timing (+0/-1/💬1)
1 issues received 1 new comments:
- #165 Should 404 codes be considered aborts? (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/165 [requires Fetch integration]
1 issues closed:
- Should 404 codes be considered aborts? https://github.com/w3c/resource-timing/issues/165 [requires Fetch integration]
* w3c/navigation-timing (+0/-0/💬1)
1 issues received 1 new comments:
- #115 Definition of "back_forward" navigation type does not make sense (1 by philipwalton)
https://github.com/w3c/navigation-timing/issues/115
* w3c/resource-hints (+0/-0/💬4)
1 issues received 4 new comments:
- #82 Prefetch and double-key caching (4 by annevk, kinu)
https://github.com/w3c/resource-hints/issues/82 [Prefetch]
Pull requests
-------------
* w3c/user-timing (+0/-1/💬1)
1 pull requests received 1 new comments:
- #67 [user-timing-2] Align with Web IDL specification (1 by plehegar)
https://github.com/w3c/user-timing/pull/67
1 pull requests merged:
- [user-timing-2] Align with Web IDL specification
https://github.com/w3c/user-timing/pull/67
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/hr-time
* https://github.com/w3c/performance-timeline
* https://github.com/w3c/resource-timing
* https://github.com/w3c/navigation-timing
* https://github.com/w3c/user-timing
* https://github.com/w3c/beacon
* https://github.com/w3c/page-visibility
* https://github.com/w3c/preload
* https://github.com/w3c/resource-hints
* https://github.com/w3c/requestidlecallback
* https://github.com/w3c/device-memory
* https://github.com/w3c/paint-timing
* https://github.com/w3c/longtasks
* https://github.com/w3c/server-timing
Received on Tuesday, 1 October 2019 17:01:14 UTC