- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 28 Feb 2023 17:00:47 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1pX3LL-00B2sh-8W@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+0/-0/💬4) 2 issues received 4 new comments: - #207 Cross-origin timeline support (2 by clelland, nicjansma) https://github.com/w3c/performance-timeline/issues/207 - #206 Proposal: clock-drift correction, potentially with opt-in (2 by Forchapeatl, noamr) https://github.com/w3c/performance-timeline/issues/206 * w3c/resource-timing (+0/-0/💬1) 1 issues received 1 new comments: - #210 Cross-origin IFRAME opting-in to sharing ResourceTiming data (1 by clelland) https://github.com/w3c/resource-timing/issues/210 [enhancement] [requires Fetch integration] * w3c/navigation-timing (+0/-0/💬1) 1 issues received 1 new comments: - #181 Clarify how PerformanceTiming.responseStart relates to Early Hint responses (1 by adardesign) https://github.com/w3c/navigation-timing/issues/181 * w3c/resource-hints (+1/-0/💬4) 1 issues created: - Archive this (by yoavweiss) https://github.com/w3c/resource-hints/issues/100 1 issues received 4 new comments: - #100 Archive this (4 by caribouW3, domenic, yoavweiss) https://github.com/w3c/resource-hints/issues/100 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, 28 February 2023 17:00:49 UTC