- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 15 Mar 2022 17:00:55 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1nUAXX-0002bU-3q@uranus.w3.org>
Issues ------ * w3c/navigation-timing (+1/-4/💬4) 1 issues created: - Links to "relevant application caches" are broken (by yoavweiss) https://github.com/w3c/navigation-timing/issues/173 3 issues received 4 new comments: - #173 Links to "relevant application caches" are broken (1 by yoavweiss) https://github.com/w3c/navigation-timing/issues/173 - #171 Extend Navigation Timing API to include back/forward cache NotRestoredReasons (2 by crockercliff, rubberyuzu) https://github.com/w3c/navigation-timing/issues/171 - #117 Better integration with ResourceTiming (1 by noamr) https://github.com/w3c/navigation-timing/issues/117 [clarification] 4 issues closed: - Processing Model: Should 'prompt for unload' box actually be unload? https://github.com/w3c/navigation-timing/issues/164 - AppCache meaning https://github.com/w3c/navigation-timing/issues/140 - Better integration with ResourceTiming https://github.com/w3c/navigation-timing/issues/117 [clarification] - Links to "relevant application caches" are broken https://github.com/w3c/navigation-timing/issues/173 * w3c/user-timing (+0/-2/💬6) 4 issues received 6 new comments: - #68 Allow marks and measures to be shown in developer tooling without adding it to the performance timeline (3 by yoavweiss) https://github.com/w3c/user-timing/issues/68 [enhancement] [triaged] - #40 Define best practices for monitoring of single page apps via UT / custom Entries (1 by yoavweiss) https://github.com/w3c/user-timing/issues/40 - #37 Update the introductory text to explain how this API differs from performance.now() (1 by yoavweiss) https://github.com/w3c/user-timing/issues/37 - #25 Provide a way to associate warnings with measurements (1 by yoavweiss) https://github.com/w3c/user-timing/issues/25 [whiteboard] 2 issues closed: - Provide a way to associate warnings with measurements https://github.com/w3c/user-timing/issues/25 [whiteboard] - Update the introductory text to explain how this API differs from performance.now() https://github.com/w3c/user-timing/issues/37 * w3c/preload (+0/-1/💬0) 1 issues closed: - Link header processing https://github.com/w3c/preload/issues/148 [HTML integration] * w3c/resource-hints (+0/-0/💬1) 1 issues received 1 new comments: - #86 Specify processing model in terms of Fetch (1 by noamr) https://github.com/w3c/resource-hints/issues/86 [definition] [discussion] Pull requests ------------- * w3c/navigation-timing (+3/-3/💬0) 3 pull requests submitted: - Update diagram (by noamr) https://github.com/w3c/navigation-timing/pull/175 - Update "relevant application cache" to point to HTTP cache (by noamr) https://github.com/w3c/navigation-timing/pull/174 - Rename NavigationType to NavigationTimingType (by domenic) https://github.com/w3c/navigation-timing/pull/172 3 pull requests merged: - Rename NavigationType to NavigationTimingType https://github.com/w3c/navigation-timing/pull/172 - Update diagram: rename "prompt to unload" and "AppCache" https://github.com/w3c/navigation-timing/pull/175 - Update "relevant application cache" to point to HTTP cache https://github.com/w3c/navigation-timing/pull/174 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, 15 March 2022 17:00:56 UTC