- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 05 Nov 2024 17:00:42 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1t8Mv4-007pRE-1V@janus.w3.internal>
Issues
------
* w3c/resource-timing (+0/-2/💬4)
2 issues received 4 new comments:
- #345 Consider adding finalResponseHeaders{Start|End} times (3 by noamr, tunetheweb)
https://github.com/w3c/resource-timing/issues/345
- #137 Proposal: API for exposing resource requests (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/137 [enhancement]
2 issues closed:
- Consider adding finalResponseHeaders{Start|End} times https://github.com/w3c/resource-timing/issues/345
- Consider adding finalResponseHeaders{Start|End} times https://github.com/w3c/resource-timing/issues/345
* w3c/paint-timing (+0/-2/💬0)
2 issues closed:
- Consider to expose decoding time for FCP and LCP? https://github.com/w3c/paint-timing/issues/104
- Consider to expose decoding time for FCP and LCP? https://github.com/w3c/paint-timing/issues/104
Pull requests
-------------
* w3c/hr-time (+1/-0/💬0)
1 pull requests submitted:
- Add a coarsening function for render timestamps (by noamr)
https://github.com/w3c/hr-time/pull/166
* w3c/resource-timing (+3/-3/💬3)
3 pull requests submitted:
- Update timestamp SVG (by tunetheweb)
https://github.com/w3c/resource-timing/pull/410
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/409
- Add finalResponseHeadersStart which is always the 2xx/4xx/5xx response. (by noamr)
https://github.com/w3c/resource-timing/pull/408
2 pull requests received 3 new comments:
- #409 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/409
- #408 Add finalResponseHeadersStart which is always the 2xx/4xx/5xx response. (2 by tunetheweb)
https://github.com/w3c/resource-timing/pull/408
3 pull requests merged:
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/409
- Update timestamp SVG
https://github.com/w3c/resource-timing/pull/410
- Add finalResponseHeadersStart which is always the 2xx/4xx/5xx response.
https://github.com/w3c/resource-timing/pull/408
* w3c/navigation-timing (+1/-1/💬0)
1 pull requests submitted:
- Update diagram to add finalResponseHeadersStart (by tunetheweb)
https://github.com/w3c/navigation-timing/pull/205
1 pull requests merged:
- Update diagram to add finalResponseHeadersStart
https://github.com/w3c/navigation-timing/pull/205
* w3c/user-timing (+0/-1/💬0)
1 pull requests merged:
- Remove level
https://github.com/w3c/user-timing/pull/114
* w3c/paint-timing (+1/-1/💬0)
1 pull requests submitted:
- Remove TAO check from element timing reporting (by noamr)
https://github.com/w3c/paint-timing/pull/105
1 pull requests merged:
- Remove TAO check from element timing & LCP reporting
https://github.com/w3c/paint-timing/pull/105
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, 5 November 2024 17:00:43 UTC