Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #381 Expose Content-Encoding to ResourceTiming (1 by Jxck)
    https://github.com/w3c/resource-timing/issues/381 [enhancement] [requires Fetch integration] [fetch-integration] 

* w3c/navigation-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #193 Proposal: add timestamp for when "activation" or "dismissal" starts (1 by nicjansma)
    https://github.com/w3c/navigation-timing/issues/193 

* w3c/server-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #95 PerformanceServerTiming entry always has a duration field even when the original header did not (1 by nicjansma)
    https://github.com/w3c/server-timing/issues/95 




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