- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 06 Sep 2022 17:00:55 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1oVbwV-003m9x-D5@uranus.w3.org>
Issues
------
* w3c/resource-timing (+2/-0/💬23)
2 issues created:
- InitiatorType for module scripts (by yoavweiss)
https://github.com/w3c/resource-timing/issues/346
- Consider adding finalResponseHeaders{Start|End} times (by noamr)
https://github.com/w3c/resource-timing/issues/345
1 issues received 23 new comments:
- #345 Consider adding finalResponseHeaders{Start|End} times (23 by LPardue, colinbendell, dotjs, nicjansma, noamr, tunetheweb)
https://github.com/w3c/resource-timing/issues/345
* w3c/navigation-timing (+1/-0/💬4)
1 issues created:
- Clarify how PerformanceTiming.responseStart relates to Early Hint responses (by colinbendell)
https://github.com/w3c/navigation-timing/issues/181
2 issues received 4 new comments:
- #181 Clarify how PerformanceTiming.responseStart relates to Early Hint responses (2 by LPardue, nicjansma)
https://github.com/w3c/navigation-timing/issues/181
- #180 Extend 'NavigationType' to include User Agent Launch (2 by amiyagupta, marcelduran)
https://github.com/w3c/navigation-timing/issues/180 [enhancement]
* w3c/user-timing (+0/-0/💬2)
1 issues received 2 new comments:
- #99 In workers, mark names can be PerformanceTiming attributes but they cannot be retrieved in measures (2 by paulirish, yoavweiss)
https://github.com/w3c/user-timing/issues/99
* w3c/resource-hints (+1/-1/💬1)
1 issues created:
- Owner (by chingon81)
https://github.com/w3c/resource-hints/issues/98
1 issues received 1 new comments:
- #13 Clarify `preload` with relation to `async` and `defer`? (1 by AliN11)
https://github.com/w3c/resource-hints/issues/13
1 issues closed:
- Owner https://github.com/w3c/resource-hints/issues/98
Pull requests
-------------
* w3c/resource-timing (+2/-2/💬16)
2 pull requests submitted:
- Explainer for Resource response status (by abinpaul1)
https://github.com/w3c/resource-timing/pull/347
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/344
3 pull requests received 16 new comments:
- #344 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/344
- #343 Add delivery type to PerformanceResourceTiming. (7 by jeremyroman, nicjansma, yoavweiss)
https://github.com/w3c/resource-timing/pull/343
- #341 [draft] Add content-type to resource-timing (8 by abinpaul1, domenic, yoavweiss)
https://github.com/w3c/resource-timing/pull/341
2 pull requests merged:
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/344
- Add Render Blocking Status to PerformanceResourceTiming
https://github.com/w3c/resource-timing/pull/327
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, 6 September 2022 17:00:57 UTC