- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 19 Jul 2022 17:00:53 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1oDqab-00BDZ8-Ig@uranus.w3.org>
Issues
------
* w3c/performance-timeline (+0/-1/💬1)
1 issues received 1 new comments:
- #100 Ensure tests are clean (1 by yoavweiss)
https://github.com/w3c/performance-timeline/issues/100
1 issues closed:
- Ensure tests are clean https://github.com/w3c/performance-timeline/issues/100
* w3c/resource-timing (+1/-6/💬13)
1 issues created:
- Is nexthopprotocol different from that in the chrome devtools? (by mamumu123)
https://github.com/w3c/resource-timing/issues/336
9 issues received 13 new comments:
- #336 Is nexthopprotocol different from that in the chrome devtools? (1 by nicjansma)
https://github.com/w3c/resource-timing/issues/336
- #332 Expose delivery type in PerformanceResourceTiming. (1 by noamr)
https://github.com/w3c/resource-timing/issues/332
- #304 Consider to limit the max size of resource timing buffer (1 by noamr)
https://github.com/w3c/resource-timing/issues/304
- #254 WPT Cleanup (2 by noamr, yoavweiss)
https://github.com/w3c/resource-timing/issues/254
- #233 ResourceTiming Test Triage 9/2020 (1 by noamr)
https://github.com/w3c/resource-timing/issues/233 [hackathon_15_09_20] [hackathon_2020]
- #90 Add response status codes for resources in Resource Timing API. (1 by abinpaul1)
https://github.com/w3c/resource-timing/issues/90 [enhancement] [whiteboard] [requires Fetch integration]
- #71 Transition Level 2 to CR (2 by noamr, yoavweiss)
https://github.com/w3c/resource-timing/issues/71 [w3c]
- #58 ResourceTiming and preconnect (2 by noamr, yoavweiss)
https://github.com/w3c/resource-timing/issues/58 [enhancement] [whiteboard]
- #53 Server pushed resources in ResourceTiming (2 by MattMenke2, noamr)
https://github.com/w3c/resource-timing/issues/53
6 issues closed:
- WPT Cleanup https://github.com/w3c/resource-timing/issues/254
- Transition Level 2 to CR https://github.com/w3c/resource-timing/issues/71 [w3c]
- Server pushed resources in ResourceTiming https://github.com/w3c/resource-timing/issues/53
- Consider to limit the max size of resource timing buffer https://github.com/w3c/resource-timing/issues/304
- ResourceTiming and preconnect https://github.com/w3c/resource-timing/issues/58 [enhancement] [whiteboard]
- Is nexthopprotocol different from that in the chrome devtools? https://github.com/w3c/resource-timing/issues/336
* w3c/device-memory (+0/-1/💬0)
1 issues closed:
- Should device memory be limited to what the UA can access? https://github.com/w3c/device-memory/issues/13
Pull requests
-------------
* w3c/resource-timing (+2/-2/💬2)
2 pull requests submitted:
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/338
- chore: Fix missing curly brace (by nicjansma)
https://github.com/w3c/resource-timing/pull/337
2 pull requests received 2 new comments:
- #338 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/338
- #335 Add response status code to PerfomanceResourceTiming (1 by martinthomson)
https://github.com/w3c/resource-timing/pull/335
2 pull requests merged:
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/338
- chore: Fix missing curly brace
https://github.com/w3c/resource-timing/pull/337
* w3c/device-memory (+1/-0/💬0)
1 pull requests submitted:
- Address editorial issues (by yoavweiss)
https://github.com/w3c/device-memory/pull/46
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, 19 July 2022 17:00:59 UTC