Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-1/💬5)
  1 issues received 5 new comments:
  - #56 Reducing the precision of the DOMHighResTimeStamp resolution (5 by tdresser, mdrejhon, toddreifsteck)
    https://github.com/w3c/hr-time/issues/56 [security] 

  1 issues closed:
  - Add prompt to unload test https://github.com/w3c/hr-time/issues/32 [test:missing-coverage] 

* w3c/performance-timeline (+2/-1/💬2)
  2 issues created:
  - When a UA is under memory pressure, what the proper way to shrink buffers in timeline? (by toddreifsteck)
    https://github.com/w3c/performance-timeline/issues/101 
  - Ensure tests are clean and L2 is republished after updates from Jan Triage call (by toddreifsteck)
    https://github.com/w3c/performance-timeline/issues/100 

  2 issues received 2 new comments:
  - #99 Objects with the same start time have unspecified ordering (1 by toddreifsteck)
    https://github.com/w3c/performance-timeline/issues/99 
  - #101 When a UA is under memory pressure, what the proper way to shrink buffers in timeline? (1 by toddreifsteck)
    https://github.com/w3c/performance-timeline/issues/101 

  1 issues closed:
  - Objects with the same start time have unspecified ordering https://github.com/w3c/performance-timeline/issues/99 

* w3c/resource-timing (+0/-0/💬12)
  6 issues received 12 new comments:
  - #142 `InitiatorType` should not single out XHR (6 by annevk, yoavweiss)
    https://github.com/w3c/resource-timing/issues/142 
  - #94 Clarify whether UA can clear the buffer under memory pressure (2 by yoavweiss, toddreifsteck)
    https://github.com/w3c/resource-timing/issues/94 [blocked:feedback] 
  - #70 Missing test for CSS (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/70 [blocked:feedback] [security] [test:missing-coverage] 
  - #138 initiatorType test cases (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/138 [needs tests] 
  - #12 Clarify presence of requests that don't return a response (1 by igrigorik)
    https://github.com/w3c/resource-timing/issues/12 
  - #95 Clarify resourcetimingbufferfull conditions (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/95 [Clarification] 

* w3c/user-timing (+1/-4/💬13)
  1 issues created:
  - Update the introductory text to explain how this API differs from performance.now() (by philipwalton)
    https://github.com/w3c/user-timing/issues/37 

  6 issues received 13 new comments:
  - #37 Update the introductory text to explain how this API differs from performance.now() (4 by tobie, toddreifsteck, philipwalton)
    https://github.com/w3c/user-timing/issues/37 
  - #36 Update WP tests to not throw when NT1 names are used as the first arg in measure calls (3 by igrigorik, philipwalton)
    https://github.com/w3c/user-timing/issues/36 [test:missing-coverage] 
  - #29 Existing Test gap: Verify that toJSON output is created properly (3 by igrigorik, tobie)
    https://github.com/w3c/user-timing/issues/29 [test:missing-coverage] 
  - #22 What does "navigationStart" mean as a second argument to performance.measure() in a web worker? (1 by igrigorik)
    https://github.com/w3c/user-timing/issues/22 [bug] 
  - #26 measure() may throw InvalidAccessError (1 by igrigorik)
    https://github.com/w3c/user-timing/issues/26 [bug] 
  - #31 Clarify what Navigation Timing entries are allowed and how to use their values (1 by igrigorik)
    https://github.com/w3c/user-timing/issues/31 

  4 issues closed:
  - Clarify what Navigation Timing entries are allowed and how to use their values https://github.com/w3c/user-timing/issues/31 
  - measure() may throw InvalidAccessError https://github.com/w3c/user-timing/issues/26 [bug] 
  - What does "navigationStart" mean as a second argument to performance.measure() in a web worker? https://github.com/w3c/user-timing/issues/22 [bug] 
  - measure() may throw SyntaxError https://github.com/w3c/user-timing/issues/21 [bug] 

* w3c/beacon (+1/-0/💬0)
  1 issues created:
  - Resource Timing + beacon test (by toddreifsteck)
    https://github.com/w3c/beacon/issues/58 

* w3c/preload (+0/-0/💬2)
  1 issues received 2 new comments:
  - #120 `srcset`/`sizes` attributes for selectively preloading images (2 by domenic, cramforce)
    https://github.com/w3c/preload/issues/120 



Pull requests
-------------
* w3c/hr-time (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #55 Decreased DOMHighResTimeStamp resolution (1 by mdrejhon)
    https://github.com/w3c/hr-time/pull/55 [enhancement] [security] 

* w3c/resource-timing (+1/-0/💬1)
  1 pull requests submitted:
  - Add a note regarding navigation preload in initiatorType (by yoavweiss)
    https://github.com/w3c/resource-timing/pull/147 

  1 pull requests received 1 new comments:
  - #128 V2 (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/pull/128 

* w3c/user-timing (+0/-1/💬2)
  1 pull requests received 2 new comments:
  - #35 Address outstanding L2 issues (2 by toddreifsteck, philipwalton)
    https://github.com/w3c/user-timing/pull/35 

  1 pull requests merged:
  - Address outstanding L2 issues
    https://github.com/w3c/user-timing/pull/35 


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