Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/longtasks (+2/-0/💬4)
  2 issues created:
  - Overloading PerformanceEntry (by Elchi3)
    https://github.com/w3c/longtasks/issues/133 
  - Consider to have a separate spec for Long Animation Frame API (by sefeng211)
    https://github.com/w3c/longtasks/issues/132 

  2 issues received 4 new comments:
  - #132 Consider to have a separate spec for Long Animation Frame API (2 by caribouW3, yoavweiss)
    https://github.com/w3c/longtasks/issues/132 
  - #115 [LoAF] Should it be easier to link LoAF to INP entries (2 by lebreRafael, noamr)
    https://github.com/w3c/longtasks/issues/115 



Pull requests
-------------
* w3c/performance-timeline (+1/-0/💬0)
  1 pull requests submitted:
  - The common atttribute of `PerformanceEntry` should be initialized rat… (by noamr)
    https://github.com/w3c/performance-timeline/pull/210 


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