- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 18 Dec 2018 17:00:42 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1gZIja-0008TZ-A4@uranus.w3.org>
Issues
------
* w3c/hr-time (+0/-0/💬3)
2 issues received 3 new comments:
- #60 Security Review (2 by plehegar, yoavweiss)
https://github.com/w3c/hr-time/issues/60
- #20 PLING review (1 by plehegar)
https://github.com/w3c/hr-time/issues/20 [privacy]
* w3c/resource-timing (+3/-1/💬12)
3 issues created:
- Test multiple DNS responses and connection failures (by yoavweiss)
https://github.com/w3c/resource-timing/issues/188
- Test domainLookup values in the connection coalescing case (by yoavweiss)
https://github.com/w3c/resource-timing/issues/186
- Many of the tests are flaky (by yoavweiss)
https://github.com/w3c/resource-timing/issues/182
8 issues received 12 new comments:
- #87 Ensure that first byte measurement and 1XX responses are covered by tests (3 by acomminos, yoavweiss)
https://github.com/w3c/resource-timing/issues/87 [test:missing-coverage]
- #120 TFO and secureConnectionStart (2 by yoavweiss)
https://github.com/w3c/resource-timing/issues/120 [Clarification]
- #123 How do dns and connectStart handle multiple ip/name options? (2 by yoavweiss)
https://github.com/w3c/resource-timing/issues/123 [Clarification]
- #70 Exposing CSS subresource URLs (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/70 [security]
- #182 Many of the tests are flaky (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/182
- #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/119 [Clarification] [needs tests] [requires Fetch integration]
- #186 Test domainLookup values in the connection coalescing case (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/186 [test:missing-coverage]
- #188 Test multiple DNS responses and connection failures (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/188
1 issues closed:
- Ensure that first byte measurement and 1XX responses are covered by tests https://github.com/w3c/resource-timing/issues/87 [test:missing-coverage]
* w3c/longtasks (+0/-1/💬0)
1 issues closed:
- Typo https://github.com/w3c/longtasks/issues/55
Pull requests
-------------
* w3c/performance-timeline (+0/-0/💬4)
1 pull requests received 4 new comments:
- #112 Add |type| to PerformanceObserverInit (4 by igrigorik, npm1)
https://github.com/w3c/performance-timeline/pull/112
* w3c/resource-timing (+5/-1/💬0)
5 pull requests submitted:
- Clarify that connectStart/connectEnd refer to the latest connection retry (by yoavweiss)
https://github.com/w3c/resource-timing/pull/189
- Address the request retry case, and add a note (by yoavweiss)
https://github.com/w3c/resource-timing/pull/187
- Connection reuse does not imply DNS was not required (by yoavweiss)
https://github.com/w3c/resource-timing/pull/185
- Fix "can add entry" algorithm typo which made it incorrect (by yoavweiss)
https://github.com/w3c/resource-timing/pull/184
- Add a note regarding negative timestamps for navigation preload requests (by yoavweiss)
https://github.com/w3c/resource-timing/pull/183
1 pull requests merged:
- Fix "can add entry" algorithm typo which made it incorrect
https://github.com/w3c/resource-timing/pull/184
* w3c/user-timing (+0/-0/💬11)
1 pull requests received 11 new comments:
- #46 User Timing L3 changes (11 by igrigorik, npm1, siusin)
https://github.com/w3c/user-timing/pull/46
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, 18 December 2018 17:00:44 UTC