- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 17 Jan 2017 17:00:07 +0000
- To: public-web-perf@w3.org
Issues
------
* w3c/performance-timeline (+0/-0/💬4)
2 issues received 4 new comments:
- #56 Ability to observers past set of performance entries (3 by
igrigorik, rniwa)
https://github.com/w3c/performance-timeline/issues/56
- #64 Lack of feature detection option for new entry types (1 by
igrigorik)
https://github.com/w3c/performance-timeline/issues/64
* w3c/resource-timing (+0/-0/💬6)
2 issues received 6 new comments:
- #53 Server pushed resources in ResourceTiming (4 by igrigorik,
valour01)
https://github.com/w3c/resource-timing/issues/53
- #89 Increase limit of 150 for PerformanceEntrys? (2 by
nolanlawson)
https://github.com/w3c/resource-timing/issues/89
Pull requests
-------------
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
Received on Tuesday, 17 January 2017 17:00:43 UTC