- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 12 Jan 2021 17:00:47 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1kzN2F-0000xH-Fq@uranus.w3.org>
Issues
------
* w3c/resource-timing (+0/-2/💬2)
2 issues received 2 new comments:
- #239 Why not consider to add "fetchStart" event? (1 by nicjansma)
https://github.com/w3c/resource-timing/issues/239
- #237 Are fetchStart, connectStart, redirectStart relative to navigationStart? (1 by nicjansma)
https://github.com/w3c/resource-timing/issues/237
2 issues closed:
- Are fetchStart, connectStart, redirectStart relative to navigationStart? https://github.com/w3c/resource-timing/issues/237
- Why not consider to add "fetchStart" event? https://github.com/w3c/resource-timing/issues/239
* w3c/navigation-timing (+0/-1/💬1)
1 issues received 1 new comments:
- #132 a bit confused with the "Redirect" timing in Time Navigation (1 by nicjansma)
https://github.com/w3c/navigation-timing/issues/132
1 issues closed:
- a bit confused with the "Redirect" timing in Time Navigation https://github.com/w3c/navigation-timing/issues/132
* w3c/preload (+1/-0/💬0)
1 issues created:
- Spec should more clearly when events should be fired at preload links. (by emilio)
https://github.com/w3c/preload/issues/155
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, 12 January 2021 17:00:49 UTC