Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+1/-0/💬4)
  1 issues created:
  - Gate Timestamps behind existing permission prompts (by snyderp)
    https://github.com/w3c/hr-time/issues/64 

  2 issues received 4 new comments:
  - #64 Gate Timestamps behind existing permission prompts (2 by snyderp, yoavweiss)
    https://github.com/w3c/hr-time/issues/64 
  - #20 Privacy (PING) review (2 by snyderp, samuelweiler)
    https://github.com/w3c/hr-time/issues/20 [privacy] 

* w3c/performance-timeline (+0/-0/💬2)
  2 issues received 2 new comments:
  - #113 supported entry types needs to be context aware (1 by toddreifsteck)
    https://github.com/w3c/performance-timeline/issues/113 
  - #110 Broken link to non-existent anchor in WebIDL spec (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/110 

* w3c/resource-timing (+1/-0/💬1)
  1 issues created:
  - Include Content Type (by Snugug)
    https://github.com/w3c/resource-timing/issues/203 

  1 issues received 1 new comments:
  - #71 Transition Level 2 to CR (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/71 [w3c] 

* w3c/navigation-timing (+1/-1/💬4)
  1 issues created:
  - Applying "timing allow check" to a document makes no sense (by bzbarsky)
    https://github.com/w3c/navigation-timing/issues/104 

  3 issues received 4 new comments:
  - #85 Should navigationEntry's navigationType be updated according to the parent page ? (2 by yoavweiss, toddreifsteck)
    https://github.com/w3c/navigation-timing/issues/85 [discuss] [test:missing-coverage] 
  - #83 should unloaded iframes be included in their parent document's unload duration? (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/83 [discuss] [test:missing-coverage] 
  - #102 supported entry types needs to be context aware (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/102 [discuss] 

  1 issues closed:
  - Unload event TAO check should be for all redirects https://github.com/w3c/navigation-timing/issues/95 [discuss] [pending PR and tests] 

* w3c/user-timing (+0/-6/💬11)
  8 issues received 11 new comments:
  - #15 Enable association with input events. (3 by npm1, tdresser, yoavweiss)
    https://github.com/w3c/user-timing/issues/15 [whiteboard] 
  - #17 Declarative marks (2 by npm1, yoavweiss)
    https://github.com/w3c/user-timing/issues/17 [whiteboard] 
  - #43 Level 3 proposal (1 by npm1)
    https://github.com/w3c/user-timing/issues/43 
  - #14 Handling repeat metrics and measures + custom startTime? (1 by npm1)
    https://github.com/w3c/user-timing/issues/14 [whiteboard] 
  - #48 Measure API: make startOrOptions nullable (1 by npm1)
    https://github.com/w3c/user-timing/issues/48 
  - #23 mark() and measure() return PerformanceEntries (1 by npm1)
    https://github.com/w3c/user-timing/issues/23 [enhancement] 
  - #25 Provide a way to associate warnings with measurements (1 by npm1)
    https://github.com/w3c/user-timing/issues/25 [whiteboard] 
  - #27 Should performance.measure() work with resource timing entries? (1 by npm1)
    https://github.com/w3c/user-timing/issues/27 [whiteboard] 

  6 issues closed:
  - Enable association with input events. https://github.com/w3c/user-timing/issues/15 [whiteboard] 
  - Handling repeat metrics and measures + custom startTime? https://github.com/w3c/user-timing/issues/14 [whiteboard] 
  - mark() and measure() return PerformanceEntries https://github.com/w3c/user-timing/issues/23 [enhancement] 
  - Should performance.measure() work with resource timing entries? https://github.com/w3c/user-timing/issues/27 [whiteboard] 
  - Measure API: make startOrOptions nullable https://github.com/w3c/user-timing/issues/48 
  - Level 3 proposal https://github.com/w3c/user-timing/issues/43 



Pull requests
-------------
* w3c/navigation-timing (+1/-1/💬1)
  1 pull requests submitted:
  - Make sure all redirects pass TAO before exposing unload data (by yoavweiss)
    https://github.com/w3c/navigation-timing/pull/103 

  1 pull requests received 1 new comments:
  - #103 Make sure all redirects pass TAO before exposing unload data (1 by toddreifsteck)
    https://github.com/w3c/navigation-timing/pull/103 

  1 pull requests merged:
  - Make sure all redirects pass TAO before exposing unload data
    https://github.com/w3c/navigation-timing/pull/103 


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