- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 04 Apr 2017 17:00:17 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1cvRoX-00087M-Va@uranus.w3.org>
Issues
------
* w3c/performance-timeline (+0/-1/💬0)
1 issues closed:
- Redundant throw should be removed https://github.com/w3c/performance-timeline/issues/73
* w3c/resource-timing (+2/-0/💬0)
2 issues created:
- Prose link to PerformanceEntry is broken (by annevk)
https://github.com/w3c/resource-timing/issues/108
- Link PerformanceEntry in IDL (by annevk)
https://github.com/w3c/resource-timing/issues/107
* w3c/navigation-timing (+3/-0/💬1)
3 issues created:
- Please fix at least your broken links, if you want anyone to ever make any sense of your specs (by bzbarsky)
https://github.com/w3c/navigation-timing/issues/65
- IDL should xref PerformanceResourceTiming (by annevk)
https://github.com/w3c/navigation-timing/issues/64
- Please integrate directly with HTML (by annevk)
https://github.com/w3c/navigation-timing/issues/63
1 issues received 1 new comments:
- #63 Please integrate directly with HTML (1 by plehegar)
https://github.com/w3c/navigation-timing/issues/63
* w3c/user-timing (+2/-0/💬1)
2 issues created:
- Should performance.measure() work with resource timing entries? (by philipwalton)
https://github.com/w3c/user-timing/issues/27
- measure() may throw InvalidAccessError (by plehegar)
https://github.com/w3c/user-timing/issues/26
1 issues received 1 new comments:
- #27 Should performance.measure() work with resource timing entries? (1 by igrigorik)
https://github.com/w3c/user-timing/issues/27
* w3c/page-visibility (+1/-1/💬2)
1 issues created:
- Typo: s/intellegently/intelligently/ (by austinsims)
https://github.com/w3c/page-visibility/issues/30
1 issues closed:
- Typo: s/intellegently/intelligently/ https://github.com/w3c/page-visibility/issues/30
2 issues received 2 new comments:
- #29 Log if a page was ever visible (1 by igrigorik)
https://github.com/w3c/page-visibility/issues/29
- #30 Typo: s/intellegently/intelligently/ (1 by igrigorik)
https://github.com/w3c/page-visibility/issues/30
* w3c/preload (+0/-1/💬8)
1 issues closed:
- Add support for cache busting via etag header https://github.com/w3c/preload/issues/68
3 issues received 8 new comments:
- #83 Tighter definition of "load was successful" (4 by annevk, hillbrad, yoavweiss)
https://github.com/w3c/preload/issues/83
- #68 Add support for cache busting via etag header (2 by drzraf, yoavweiss)
https://github.com/w3c/preload/issues/68
- #84 Difference between Link: rel=preload header and the link HTML element (2 by igrigorik, yoavweiss)
https://github.com/w3c/preload/issues/84
Pull requests
-------------
* w3c/performance-timeline (+1/-2/💬9)
1 pull requests submitted:
- buffer only until `onload`, add references to server-timing, add 'bufferedTypes' param (by cvazac)
https://github.com/w3c/performance-timeline/pull/76
2 pull requests merged:
- Fixup: ReSpec warnings, structure, etc.
https://github.com/w3c/performance-timeline/pull/72
- Refactor, shuffle order, improve navigation
https://github.com/w3c/performance-timeline/pull/75
2 pull requests received 9 new comments:
- #76 buffer only until `onload`, add references to server-timing, add `bufferedTypes` param (7 by igrigorik, dontcallmedom, cvazac, yoavweiss)
https://github.com/w3c/performance-timeline/pull/76
- #75 Refactor, shuffle order, improve navigation (2 by plehegar)
https://github.com/w3c/performance-timeline/pull/75
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, 4 April 2017 17:00:24 UTC