Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-0/💬9)
  2 issues received 9 new comments:
  - #79 Security and privacy considerations for DOMHighResTimeStamp resolution (6 by igrigorik, snyderp, samuelweiler, yoavweiss, tomlowenthal)
    https://github.com/w3c/hr-time/issues/79 [privacy] [security] 
  - #20 Privacy (PING) review (3 by igrigorik, samuelweiler, yoavweiss)
    https://github.com/w3c/hr-time/issues/20 [privacy] 

* w3c/performance-timeline (+1/-2/💬4)
  1 issues created:
  - `buffered: true` not adding entries to PerformanceObserver's buffer (by hsm2)
    https://github.com/w3c/performance-timeline/issues/145 

  3 issues received 4 new comments:
  - #145 `buffered: true` not adding entries to PerformanceObserver's buffer (2 by tdresser, npm1)
    https://github.com/w3c/performance-timeline/issues/145 
  - #128 How does "queue a PerformanceEntry" algorithm interact with other specs? (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/128 
  - #130 "relevant performance entry tuple" usage is still broken (1 by bzbarsky)
    https://github.com/w3c/performance-timeline/issues/130 

  2 issues closed:
  - `buffered: true` not adding entries to PerformanceObserver's buffer https://github.com/w3c/performance-timeline/issues/145 
  - How does "queue a PerformanceEntry" algorithm interact with other specs? https://github.com/w3c/performance-timeline/issues/128 

* w3c/navigation-timing (+0/-1/💬0)
  1 issues closed:
  - secureConnectionStart definition is inconsistent with ResourceTiming https://github.com/w3c/navigation-timing/issues/84 

* w3c/preload (+1/-0/💬7)
  1 issues created:
  - Specifying Range in Link preload header for HTTP/2 Push (by roger-on-github)
    https://github.com/w3c/preload/issues/139 

  1 issues received 7 new comments:
  - #139 Specifying Range in Link preload header for HTTP/2 Push (7 by annevk, roger-on-github, yoavweiss, wilaw)
    https://github.com/w3c/preload/issues/139 

* w3c/longtasks (+0/-0/💬7)
  2 issues received 7 new comments:
  - #41 Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? (6 by nicjansma, npm1, philipwalton)
    https://github.com/w3c/longtasks/issues/41 [requires-discussion] 
  - #26 PerformanceTimeline support (1 by nicjansma)
    https://github.com/w3c/longtasks/issues/26 [enhancement] [requires-discussion] 



Pull requests
-------------
* w3c/performance-timeline (+2/-2/💬0)
  2 pull requests submitted:
  - Fix input ordering (by npm1)
    https://github.com/w3c/performance-timeline/pull/144 
  - Add a basic explainer (by npm1)
    https://github.com/w3c/performance-timeline/pull/143 

  2 pull requests merged:
  - Fix input ordering
    https://github.com/w3c/performance-timeline/pull/144 
  - Add a basic explainer
    https://github.com/w3c/performance-timeline/pull/143 

* w3c/navigation-timing (+0/-1/💬5)
  2 pull requests received 5 new comments:
  - #106 Avoid redefining secureConnectionStart (4 by npm1, yoavweiss)
    https://github.com/w3c/navigation-timing/pull/106 
  - #92 Fold the secureConnectionStart processing to ResourceTiming's processing (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/pull/92 

  1 pull requests merged:
  - Avoid redefining secureConnectionStart
    https://github.com/w3c/navigation-timing/pull/106 

* w3c/user-timing (+1/-0/💬5)
  1 pull requests submitted:
  - Giving startOrOptions a default value for IDL conformance. (by tommckee1)
    https://github.com/w3c/user-timing/pull/65 

  1 pull requests received 5 new comments:
  - #65 Giving startOrOptions a default value for IDL conformance. (5 by marcoscaceres, tommckee1, npm1)
    https://github.com/w3c/user-timing/pull/65 

* w3c/page-visibility (+0/-0/💬2)
  2 pull requests received 2 new comments:
  - #45 Correct reference of Page Visibility to top level browsing context (1 by yoavweiss)
    https://github.com/w3c/page-visibility/pull/45 
  - #46 Allow a user agent to return hidden when obscured (1 by yoavweiss)
    https://github.com/w3c/page-visibility/pull/46 

* w3c/requestidlecallback (+0/-1/💬0)
  1 pull requests merged:
  - Clarify timeRemaining() algorithm.
    https://github.com/w3c/requestidlecallback/pull/79 


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