Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (1 by marcelduran)
    https://github.com/w3c/resource-timing/issues/119 [Clarification] [needs tests] [requires Fetch integration] 

* w3c/navigation-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #124 What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? (1 by makotoshimazu)
    https://github.com/w3c/navigation-timing/issues/124 




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