- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 26 Jun 2018 17:00:33 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1fXrKT-0007e8-N1@uranus.w3.org>
Issues
------
* w3c/resource-timing (+0/-0/💬9)
3 issues received 9 new comments:
- #96 Clarify behavior of setResourceTimingBufferSize (6 by npm1, yoavweiss, wanderview)
https://github.com/w3c/resource-timing/issues/96 [discuss_180618] [test:missing-coverage]
- #100 Clarify what constitutes a "downloadable resource" (2 by igrigorik, yoavweiss)
https://github.com/w3c/resource-timing/issues/100 [Clarification] [discuss_180618] [needs tests]
- #122 NextHopProtocol Values (1 by MikeBishop)
https://github.com/w3c/resource-timing/issues/122 [Clarification]
* w3c/preload (+1/-0/💬0)
1 issues created:
- Consider removing mention of high-priority fetch (by domfarolino)
https://github.com/w3c/preload/issues/125
* w3c/resource-hints (+1/-0/💬0)
1 issues created:
- Dead references to `pr` attribute (by jakub-g)
https://github.com/w3c/resource-hints/issues/81
* w3c/longtasks (+0/-0/💬1)
1 issues received 1 new comments:
- #41 Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? (1 by tdresser)
https://github.com/w3c/longtasks/issues/41
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, 26 June 2018 17:00:37 UTC