- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Tue, 13 Jan 2026 17:00:57 +0000
- To: public-web-perf@w3.org
- Message-ID: <176832365709.1327705.2652263462682636365@ip-10-0-1-136.ec2.internal>
Issues
------
* w3c/device-memory (+0/-0/💬5)
1 issues received 5 new comments:
- #50 Update recommended upper and lower bounds (5 by guohuideng2024, mmocny, tunetheweb)
https://github.com/w3c/device-memory/issues/50
Pull requests
-------------
* w3c/device-memory (+1/-0/💬1)
1 pull requests submitted:
- 53 (by guohuideng2024)
https://github.com/w3c/device-memory/pull/53
1 pull requests received 1 new comments:
- #53 Emphasize the bounds can be dymanically adjusted by implements (1 by guohuideng2024)
https://github.com/w3c/device-memory/pull/53
* w3c/paint-timing (+1/-0/💬0)
1 pull requests submitted:
- 120 (by tunetheweb)
https://github.com/w3c/paint-timing/pull/120
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
* https://github.com/w3c/long-animation-frames
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 January 2026 17:00:57 UTC