Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+1/-0/💬3)
  1 issues created:
  - Reflect preload information (in ResourceTiming?) (by noamr)
    https://github.com/w3c/resource-timing/issues/303 

  1 issues received 3 new comments:
  - #303 Reflect preload information (in ResourceTiming?) (3 by noamr, yoavweiss)
    https://github.com/w3c/resource-timing/issues/303 

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

* w3c/preload (+0/-0/💬1)
  1 issues received 1 new comments:
  - #97 Define the "Preload Cache" (1 by noamr)
    https://github.com/w3c/preload/issues/97 [HTML integration] 

* w3c/requestidlecallback (+1/-1/💬0)
  1 issues created:
  - Suggestion: expose specific information instead of deadline (by noamr)
    https://github.com/w3c/requestidlecallback/issues/97 

  1 issues closed:
  - Relying on an event loop might restart an idle period for each task https://github.com/w3c/requestidlecallback/issues/96 

* w3c/server-timing (+2/-0/💬1)
  2 issues created:
  - Make it clearer what the units for `duration` are (by npm1)
    https://github.com/w3c/server-timing/issues/86 
  - Should PerformanceServerTiming inherit from PerformanceEntry? (by npm1)
    https://github.com/w3c/server-timing/issues/85 

  1 issues received 1 new comments:
  - #86 Make it clearer what the units for `duration` are (1 by npm1)
    https://github.com/w3c/server-timing/issues/86 



Pull requests
-------------
* w3c/hr-time (+1/-0/💬3)
  1 pull requests submitted:
  - Expose everywhere (by Ms2ger)
    https://github.com/w3c/hr-time/pull/130 

  1 pull requests received 3 new comments:
  - #130 Expose everywhere (3 by w3cbot, yoavweiss)
    https://github.com/w3c/hr-time/pull/130 

* w3c/performance-timeline (+1/-0/💬1)
  1 pull requests submitted:
  - Expose everywhere (by Ms2ger)
    https://github.com/w3c/performance-timeline/pull/193 

  1 pull requests received 1 new comments:
  - #193 Expose everywhere (1 by npm1)
    https://github.com/w3c/performance-timeline/pull/193 

* w3c/resource-timing (+1/-0/💬0)
  1 pull requests submitted:
  - Expose everywhere (by Ms2ger)
    https://github.com/w3c/resource-timing/pull/302 

* w3c/user-timing (+1/-0/💬0)
  1 pull requests submitted:
  - Expose everywhere (by Ms2ger)
    https://github.com/w3c/user-timing/pull/85 

* w3c/server-timing (+1/-0/💬0)
  1 pull requests submitted:
  - Expose everywhere (by Ms2ger)
    https://github.com/w3c/server-timing/pull/84 


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