- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 03 Oct 2017 17:00:46 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1dzQYo-00064w-Mf@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+0/-1/💬3) 1 issues received 3 new comments: - #83 Existing Test gap: Verify that toJSON output is created properly (3 by igrigorik, plehegar, toddreifsteck) https://github.com/w3c/performance-timeline/issues/83 1 issues closed: - Existing Test gap: Verify that toJSON output is created properly https://github.com/w3c/performance-timeline/issues/83 * w3c/resource-timing (+0/-3/💬3) 2 issues received 3 new comments: - #115 Existing Test gap: Verify that toJSON is created properly (2 by igrigorik, plehegar) https://github.com/w3c/resource-timing/issues/115 - #98 Graphic should indicate fetchStart is a required field, not a parenthesized zeroed field (1 by plehegar) https://github.com/w3c/resource-timing/issues/98 3 issues closed: - Existing Test gap: Verify that toJSON is created properly https://github.com/w3c/resource-timing/issues/115 - Graphic should indicate fetchStart is a required field, not a parenthesized zeroed field https://github.com/w3c/resource-timing/issues/98 - Prose link to PerformanceEntry is broken https://github.com/w3c/resource-timing/issues/108 * w3c/navigation-timing (+0/-1/💬3) 1 issues received 3 new comments: - #74 Existing Test gap: Verify that toJSON is created properly (3 by igrigorik, plehegar) https://github.com/w3c/navigation-timing/issues/74 1 issues closed: - Existing Test gap: Verify that toJSON is created properly https://github.com/w3c/navigation-timing/issues/74 * w3c/user-timing (+0/-0/💬1) 1 issues received 1 new comments: - #23 mark() and measure() return PerformanceEntries (1 by philipwalton) https://github.com/w3c/user-timing/issues/23 * w3c/beacon (+3/-2/💬3) 3 issues created: - Typo in Privacy and Security (by JosephPecoraro) https://github.com/w3c/beacon/issues/57 - Typo in Processing Model - fetch step (by JosephPecoraro) https://github.com/w3c/beacon/issues/56 - Typo in Introduction note (by JosephPecoraro) https://github.com/w3c/beacon/issues/55 3 issues received 3 new comments: - #56 Typo in Processing Model - fetch step (1 by igrigorik) https://github.com/w3c/beacon/issues/56 - #41 Tests for CORS and sendBeacon() (1 by igrigorik) https://github.com/w3c/beacon/issues/41 - #57 Typo in Privacy and Security (1 by igrigorik) https://github.com/w3c/beacon/issues/57 2 issues closed: - Typo in Privacy and Security https://github.com/w3c/beacon/issues/57 - Typo in Processing Model - fetch step https://github.com/w3c/beacon/issues/56 * w3c/preload (+1/-1/💬1) 1 issues created: - Performance impact? (by edent) https://github.com/w3c/preload/issues/112 1 issues received 1 new comments: - #112 Performance impact? (1 by yoavweiss) https://github.com/w3c/preload/issues/112 1 issues closed: - Performance impact? https://github.com/w3c/preload/issues/112 * w3c/paint-timing (+1/-1/💬7) 1 issues created: - Naming of entries is inconsistent with the Navigation Timing API (by thomas-darling) https://github.com/w3c/paint-timing/issues/18 2 issues received 7 new comments: - #18 Naming of entries is inconsistent with the Navigation Timing API (4 by igrigorik, thomas-darling, domenic) https://github.com/w3c/paint-timing/issues/18 - #14 Headings should be sentence case, not titlecase (3 by thomas-darling, domenic) https://github.com/w3c/paint-timing/issues/14 1 issues closed: - Naming of entries is inconsistent with the Navigation Timing API https://github.com/w3c/paint-timing/issues/18 * w3c/server-timing (+0/-0/💬3) 1 issues received 3 new comments: - #32 Incorporating feedback from TAG review (3 by reschke, triblondon, cvazac) https://github.com/w3c/server-timing/issues/32 Pull requests ------------- * w3c/performance-timeline (+0/-0/💬4) 1 pull requests received 4 new comments: - #88 observing an empty sequence of entryTypes is a no-op (4 by igrigorik, plehegar, yoavweiss) https://github.com/w3c/performance-timeline/pull/88 * w3c/resource-timing (+1/-1/💬1) 1 pull requests submitted: - fetchStart is a required field, not a parenthesized zeroed field (by plehegar) https://github.com/w3c/resource-timing/pull/117 1 pull requests received 1 new comments: - #117 fetchStart is a required field, not a parenthesized zeroed field (1 by igrigorik) https://github.com/w3c/resource-timing/pull/117 1 pull requests merged: - fetchStart is a required field, not a parenthesized zeroed field https://github.com/w3c/resource-timing/pull/117 * w3c/requestidlecallback (+1/-1/💬2) 1 pull requests submitted: - Fix typo in index.html (by piperchester) https://github.com/w3c/requestidlecallback/pull/66 1 pull requests received 2 new comments: - #66 Fix typo in index.html (2 by plehegar) https://github.com/w3c/requestidlecallback/pull/66 1 pull requests merged: - Fix typo in index.html https://github.com/w3c/requestidlecallback/pull/66 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, 3 October 2017 17:01:10 UTC