- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 07 Jul 2020 17:00:41 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1jsqxV-0002hf-KF@uranus.w3.org>
Issues ------ * w3c/navigation-timing (+0/-0/💬1) 1 issues received 1 new comments: - #124 What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? (1 by yoavweiss) https://github.com/w3c/navigation-timing/issues/124 * w3c/preload (+0/-0/💬5) 2 issues received 5 new comments: - #148 Link header processing (3 by domfarolino, yoavweiss) https://github.com/w3c/preload/issues/148 - #147 "Delay the load event" should happen in HTML (2 by domfarolino, marcoscaceres) https://github.com/w3c/preload/issues/147 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, 7 July 2020 17:00:44 UTC