Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/performance-timeline (+0/-0/💬4)
  1 issues received 4 new comments:
  - #212 `PerformanceObserver.supportedEntryTypes`can't be annotated with `[SameObject]` (4 by clelland, tunetheweb, yoavweiss)
    https://github.com/w3c/performance-timeline/issues/212 

* w3c/resource-timing (+1/-0/💬0)
  1 issues created:
  - Add service worker static routing API information to resource timing (by sisidovski)
    https://github.com/w3c/resource-timing/issues/389 

* w3c/user-timing (+0/-0/💬2)
  1 issues received 2 new comments:
  - #109 Add a standard track/category field to the spec (2 by and-oli, bgirard)
    https://github.com/w3c/user-timing/issues/109 

* w3c/beacon (+0/-0/💬1)
  1 issues received 1 new comments:
  - #82 Chrome, Safari and Firefox behave differently when beacon blocked by CSP (1 by clelland)
    https://github.com/w3c/beacon/issues/82 

* w3c/paint-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #62 Timestamps should be specified in an interoperative way (1 by mstange)
    https://github.com/w3c/paint-timing/issues/62 

* w3c/longtasks (+1/-1/💬0)
  1 issues created:
  - Seo (by Sanalbahis06)
    https://github.com/w3c/longtasks/issues/140 

  1 issues closed:
  - Seo https://github.com/w3c/longtasks/issues/140 




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