- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 30 Jan 2024 17:00:52 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1rUrTg-00FuGz-Mm@uranus.w3.org>
Issues ------ * w3c/resource-timing (+1/-0/💬0) 1 issues created: - Should `firstInterimResponseStart` show 0 when there is no interim response? (by tunetheweb) https://github.com/w3c/resource-timing/issues/382 * w3c/longtasks (+2/-0/💬6) 2 issues created: - The `sourceLocation` property of `PerformanceScriptTiming` is complex or ambiguous to parse (by philipwalton) https://github.com/w3c/longtasks/issues/135 - LOAF: `firstUIEventTimestamp` contains non-INP events (by tunetheweb) https://github.com/w3c/longtasks/issues/134 1 issues received 6 new comments: - #134 LoAF: `firstUIEventTimestamp` contains non-INP events (6 by anatdagan, mmocny, tunetheweb, vanderhoop) https://github.com/w3c/longtasks/issues/134 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, 30 January 2024 17:00:55 UTC