Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #102 Expose a way to link a call to fetch to an individual PerformanceResourceTiming object  (1 by cdaringe)
    https://github.com/w3c/resource-timing/issues/102 [enhancement] [requires Fetch integration] 

* w3c/navigation-timing (+0/-1/💬1)
  1 issues received 1 new comments:
  - #179 Detecting whether a navigation was BFCache-eligible (1 by fergald)
    https://github.com/w3c/navigation-timing/issues/179 

  1 issues closed:
  - Should pages with different COOP be able to get unload event start/end. https://github.com/w3c/navigation-timing/issues/169 

* w3c/page-visibility (+0/-0/💬1)
  1 issues received 1 new comments:
  - #74 Spec got folded into HTML (1 by yoavweiss)
    https://github.com/w3c/page-visibility/issues/74 



Pull requests
-------------
* w3c/resource-timing (+1/-0/💬2)
  1 pull requests submitted:
  - Add Render Blocking Status to PerformanceResourceTiming (by abinpaul1)
    https://github.com/w3c/resource-timing/pull/327 

  1 pull requests received 2 new comments:
  - #327 Add Render Blocking Status to PerformanceResourceTiming (2 by caribouW3, yoavweiss)
    https://github.com/w3c/resource-timing/pull/327 


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