- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 11 Sep 2018 17:00:27 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1fzm1b-0001sY-Nz@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+0/-0/💬7) 2 issues received 7 new comments: - #103 PerformanceObserver's observe() should support entryType-specific parameters (6 by rniwa, igrigorik, npm1) https://github.com/w3c/performance-timeline/issues/103 - #106 Is the "Dependencies" section relevant? (1 by igrigorik) https://github.com/w3c/performance-timeline/issues/106 * w3c/resource-timing (+0/-0/💬4) 1 issues received 4 new comments: - #162 consider adding attributes to track Cache API performance in a service worker FetchEvent handler (4 by yoavweiss, wanderview) https://github.com/w3c/resource-timing/issues/162 Pull requests ------------- * w3c/performance-timeline (+0/-0/💬3) 1 pull requests received 3 new comments: - #104 Add entryType-specific parameters for observe() (3 by rniwa, npm1) https://github.com/w3c/performance-timeline/pull/104 * w3c/resource-timing (+0/-0/💬5) 1 pull requests received 5 new comments: - #163 Fire `resourcetimingbufferfull` asynchronously (5 by rniwa, npm1, yoavweiss) https://github.com/w3c/resource-timing/pull/163 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, 11 September 2018 17:00:34 UTC