- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 30 Apr 2024 17:00:37 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1s1qqL-008kVd-1m@janus.w3.internal>
Issues
------
* w3c/resource-timing (+0/-1/💬3)
1 issues received 3 new comments:
- #386 Should data: urls be reported in resource timing? (3 by clelland, noamr)
https://github.com/w3c/resource-timing/issues/386
1 issues closed:
- Should data: urls be reported in resource timing? https://github.com/w3c/resource-timing/issues/386
Pull requests
-------------
* w3c/resource-timing (+2/-2/💬1)
2 pull requests submitted:
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/388
- Correct clarification for data: URIs (by noamr)
https://github.com/w3c/resource-timing/pull/387
1 pull requests received 1 new comments:
- #388 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/388
2 pull requests merged:
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/388
- Correct clarification for data: URIs
https://github.com/w3c/resource-timing/pull/387
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, 30 April 2024 17:00:38 UTC