Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/navigation-timing (+0/-0/💬3)
  1 issues received 3 new comments:
  - #160 Using navigationStart as a baseline may expose cross-origin timing information (3 by mmocny, noamr, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/160 

* w3c/user-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #126 Add entry to the performance entry buffer in `mark()` and `measure()` seems excessive (1 by mmocny)
    https://github.com/w3c/user-timing/issues/126 




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
* https://github.com/w3c/long-animation-frames


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config