- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 12 Nov 2019 17:00:34 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1iUZWs-0004AS-3H@uranus.w3.org>
Issues
------
* w3c/resource-timing (+0/-0/💬3)
1 issues received 3 new comments:
- #199 Handling of 0-RTT interactions (3 by Hexcles, davidben, foolip)
https://github.com/w3c/resource-timing/issues/199
* w3c/requestidlecallback (+2/-0/💬2)
2 issues created:
- timeRemaining() step 4 should define what it means to have a "time-critical task pending" (by rniwa)
https://github.com/w3c/requestidlecallback/issues/87
- 6.2. step 1 should be defined in terms of task sources having tasks enqueued (by rniwa)
https://github.com/w3c/requestidlecallback/issues/86
1 issues received 2 new comments:
- #71 "deadline" in the "start an idle period algorithm" should be defined in terms of event loop (2 by rniwa)
https://github.com/w3c/requestidlecallback/issues/71
Pull requests
-------------
* w3c/hr-time (+0/-1/💬0)
1 pull requests merged:
- Some minor editorial changes
https://github.com/w3c/hr-time/pull/82
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, 12 November 2019 17:00:35 UTC