- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 17 May 2022 17:00:51 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1nr0Z1-0005Ez-JB@uranus.w3.org>
Issues
------
* w3c/navigation-timing (+1/-1/💬3)
1 issues created:
- Detecting whether a navigation was BFCache-eligible (by fergald)
https://github.com/w3c/navigation-timing/issues/179
3 issues received 3 new comments:
- #178 Extend the navigationType enum to include "reload after being discarded" navigations (1 by yoavweiss)
https://github.com/w3c/navigation-timing/issues/178
- #177 Report that Critical-CH was used to restart a navigation (1 by nicjansma)
https://github.com/w3c/navigation-timing/issues/177
- #163 How should prefetch be exposed? (1 by nicjansma)
https://github.com/w3c/navigation-timing/issues/163
1 issues closed:
- Extend the navigationType enum to include "reload after being discarded" navigations https://github.com/w3c/navigation-timing/issues/178
* w3c/user-timing (+0/-0/💬4)
2 issues received 4 new comments:
- #88 Marking and measuring style computation, layout calculations, etc (3 by mmocny, nhelfman, noamr)
https://github.com/w3c/user-timing/issues/88
- #86 Contextual and GC friendly user timing (1 by nicjansma)
https://github.com/w3c/user-timing/issues/86 [enhancement] [triaged]
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, 17 May 2022 17:00:56 UTC