- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 28 Apr 2020 17:00:46 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1jTTbC-0002Ko-Ol@uranus.w3.org>
Issues
------
* w3c/page-visibility (+0/-1/💬1)
1 issues received 1 new comments:
- #57 Update spec so Bikeshed can automatically pick up linkable terms (1 by marcoscaceres)
https://github.com/w3c/page-visibility/issues/57
1 issues closed:
- Update spec so Bikeshed can automatically pick up linkable terms https://github.com/w3c/page-visibility/issues/57
* w3c/preload (+1/-1/💬2)
1 issues created:
- Inconsistent load order behavior for the resources loaded with <link rel="preload"> (Chrome) (by iamskok)
https://github.com/w3c/preload/issues/146
1 issues received 2 new comments:
- #146 Inconsistent load order behavior (Chrome) (2 by domfarolino, iamskok)
https://github.com/w3c/preload/issues/146
1 issues closed:
- Inconsistent load order behavior (Chrome) https://github.com/w3c/preload/issues/146
Pull requests
-------------
* w3c/performance-timeline (+1/-1/💬0)
1 pull requests submitted:
- Use should add entry algorithm (by npm1)
https://github.com/w3c/performance-timeline/pull/166
1 pull requests merged:
- Use should add entry algorithm
https://github.com/w3c/performance-timeline/pull/166
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, 28 April 2020 17:00:49 UTC