Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/navigation-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #126 Possibility to get the HTTP status code from the Response Header ? (1 by JohnRiv)
    https://github.com/w3c/navigation-timing/issues/126 

* w3c/user-timing (+0/-1/💬5)
  2 issues received 5 new comments:
  - #69 Allow performance.measure() to specify optional color parameter, to be used by perf visualizations in devtools (3 by mathiasbynens, npm1, yoavweiss)
    https://github.com/w3c/user-timing/issues/69 [not-actionable] 
  - #68 Allow marks and measures to be shown in developer tooling without adding it to the performance timeline (2 by mathiasbynens, yoavweiss)
    https://github.com/w3c/user-timing/issues/68 [enhancement] 

  1 issues closed:
  - Allow performance.measure() to specify optional color parameter, to be used by perf visualizations in devtools https://github.com/w3c/user-timing/issues/69 [not-actionable] 

* w3c/preload (+1/-0/💬0)
  1 issues created:
  - "Delay the load event" should happen in HTML  (by marcoscaceres)
    https://github.com/w3c/preload/issues/147 

* w3c/resource-hints (+0/-0/💬1)
  1 issues received 1 new comments:
  - #13 Clarify `preload` with relation to `async` and `defer`?  (1 by Legends)
    https://github.com/w3c/resource-hints/issues/13 




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