- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Tue, 06 Jan 2026 17:00:53 +0000
- To: public-web-perf@w3.org
- Message-ID: <176771885332.595913.3362027495466241063@ip-10-0-1-136.ec2.internal>
Issues
------
* w3c/hr-time (+0/-0/💬1)
1 issues received 1 new comments:
- #164 Describe the risk of exposing additional hardware clocks (1 by EvMac0)
https://github.com/w3c/hr-time/issues/164
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, 6 January 2026 17:00:54 UTC