Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/performance-timeline (+0/-0/💬1)
  1 issues received 1 new comments:
  - #182 API shape for monitoring new navigation-like entries such as App History, BFCache, etc (1 by clelland)
    https://github.com/w3c/performance-timeline/issues/182 

* w3c/resource-timing (+1/-0/💬7)
  1 issues created:
  - Consider to limit the max size of resource timing buffer (by smaug----)
    https://github.com/w3c/resource-timing/issues/304 

  3 issues received 7 new comments:
  - #304 Consider to limit the max size of resource timing buffer (2 by npm1, yoavweiss)
    https://github.com/w3c/resource-timing/issues/304 
  - #303 Reflect preload information (in ResourceTiming?) (4 by andydavies, noamr)
    https://github.com/w3c/resource-timing/issues/303 
  - #299 Should favicon loading times be exposed to the document? (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/299 

* w3c/navigation-timing (+3/-0/💬1)
  3 issues created:
  - Using "connecStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows (by ThierryMajutec)
    https://github.com/w3c/navigation-timing/issues/165 
  - Processing Model: Should 'prompt for unload' box actually be unload? (by andydavies)
    https://github.com/w3c/navigation-timing/issues/164 
  - How should prefetch be exposed? (by jeremyroman)
    https://github.com/w3c/navigation-timing/issues/163 

  1 issues received 1 new comments:
  - #163 How should prefetch be exposed? (1 by npm1)
    https://github.com/w3c/navigation-timing/issues/163 

* w3c/page-visibility (+0/-0/💬3)
  1 issues received 3 new comments:
  - #74 Maybe we should fold this spec into HTML? (3 by caribouW3, noamr, yoavweiss)
    https://github.com/w3c/page-visibility/issues/74 

* w3c/preload (+1/-0/💬2)
  1 issues created:
  - Request parameters and preloads (by noamr)
    https://github.com/w3c/preload/issues/161 

  1 issues received 2 new comments:
  - #161 Request parameters and preloads (2 by noamr)
    https://github.com/w3c/preload/issues/161 

* w3c/requestidlecallback (+0/-0/💬1)
  1 issues received 1 new comments:
  - #97 Suggestion: expose specific information instead of deadline (1 by yoavweiss)
    https://github.com/w3c/requestidlecallback/issues/97 



Pull requests
-------------
* w3c/hr-time (+0/-0/💬2)
  1 pull requests received 2 new comments:
  - #130 Expose everywhere (2 by marcoscaceres, saschanaz)
    https://github.com/w3c/hr-time/pull/130 


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