- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 24 Jan 2017 17:00:08 +0000
- To: public-web-perf@w3.org
Issues
------
* w3c/performance-timeline (+0/-0/💬5)
1 issues received 5 new comments:
- #64 Lack of feature detection option for new entry types (5 by
igrigorik, yoavweiss, spanicker)
https://github.com/w3c/performance-timeline/issues/64
* w3c/resource-timing (+3/-0/💬6)
3 issues created:
- Determine whether to wait until after responseEnd to queue entry
for ResourceTiming (by spanicker)
https://github.com/w3c/resource-timing/issues/93
- Missing TAO tests (by igrigorik)
https://github.com/w3c/resource-timing/issues/92
- mark() and measure() return PerformanceEntries (by nolanlawson)
https://github.com/w3c/resource-timing/issues/91
3 issues received 6 new comments:
- #93 Determine whether to wait until after responseEnd to queue
entry for ResourceTiming (3 by yoavweiss, nicjansma)
https://github.com/w3c/resource-timing/issues/93
- #89 Increase limit of 150 for PerformanceEntrys? (2 by
nolanlawson, nicjansma)
https://github.com/w3c/resource-timing/issues/89
- #91 mark() and measure() return PerformanceEntries (1 by
igrigorik)
https://github.com/w3c/resource-timing/issues/91
* w3c/navigation-timing (+1/-0/💬9)
1 issues created:
- Effect of canceled navigation on navigation timing (by bripkens)
https://github.com/w3c/navigation-timing/issues/60
2 issues received 9 new comments:
- #59 Report URL in "name" attribute (instead of "document") (8 by
igrigorik, nicjansma, cvazac, toddreifsteck, spanicker)
https://github.com/w3c/navigation-timing/issues/59
- #50 data bias issues due to deferring reporting of all nav timing
metrics to the load event (1 by spanicker)
https://github.com/w3c/navigation-timing/issues/50
* w3c/preload (+1/-0/💬13)
1 issues created:
- Tighter definition of "load was successful" (by yoavweiss)
https://github.com/w3c/preload/issues/83
1 issues received 13 new comments:
- #83 Tighter definition of "load was successful" (13 by igrigorik,
annevk, yoavweiss)
https://github.com/w3c/preload/issues/83
* w3c/resource-hints (+1/-0/💬0)
1 issues created:
- Why are prefetch links optionally blockable instead of blockable?
(by bzbarsky)
https://github.com/w3c/resource-hints/issues/70
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, 24 January 2017 17:00:14 UTC