Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+1/-0/💬2)
  1 issues created:
  - Capturing basic auth credentials in URLs, part 2 (by nicjansma)
    https://github.com/w3c/resource-timing/issues/368 

  1 issues received 2 new comments:
  - #340 Problematic cases with cross-origin iframes & aborted navigations (2 by bdekoz, yoavweiss)
    https://github.com/w3c/resource-timing/issues/340 

* w3c/longtasks (+0/-0/💬1)
  1 issues received 1 new comments:
  - #80 Combination of paint timing and long tasks can expose precise paint timing (1 by noamr)
    https://github.com/w3c/longtasks/issues/80 [requires-work] 

* w3c/server-timing (+0/-0/💬2)
  1 issues received 2 new comments:
  - #43 add start time to distinguish between cached and active entries (2 by hauleth, murraylchapman)
    https://github.com/w3c/server-timing/issues/43 [enhancement] 




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