- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 03 Jan 2023 17:00:49 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1pCkef-00BjB0-Q9@uranus.w3.org>
Issues ------ * w3c/navigation-timing (+0/-2/💬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 noamr) https://github.com/w3c/navigation-timing/issues/124 [clarification] 2 issues closed: - Possibility to get the HTTP status code from the Response Header ? https://github.com/w3c/navigation-timing/issues/126 [enhancement] - What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? https://github.com/w3c/navigation-timing/issues/124 [clarification] * w3c/resource-hints (+0/-0/💬1) 1 issues received 1 new comments: - #82 Prefetch and double-key caching (1 by noamr) https://github.com/w3c/resource-hints/issues/82 [Prefetch] [Triaged] Pull requests ------------- * w3c/resource-timing (+0/-0/💬1) 1 pull requests received 1 new comments: - #366 Add interim response times (1 by yoavweiss) https://github.com/w3c/resource-timing/pull/366 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 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 January 2023 17:00:51 UTC