Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+1/-0/💬5)
  1 issues created:
  - Resource Timing Buffer/Secondary Buffer properties have vague location (by ADKaster)
    https://github.com/w3c/resource-timing/issues/414 

  2 issues received 5 new comments:
  - #381 Expose Content-Encoding to ResourceTiming (4 by guohuideng2024, pmeenan)
    https://github.com/w3c/resource-timing/issues/381 [enhancement] [requires Fetch integration] [fetch-integration] 
  - #259 Would like a precise way to map PerformanceTimings to FetchEvent (1 by monica-ch)
    https://github.com/w3c/resource-timing/issues/259 [enhancement] 




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