Weekly github digest (hr-time, performance-timeline, resource-timing, navigation-timing, user-timing, beacon, page-visibility, preload, resource-hints, requestidlecallback)

Issues
------
* w3c/performance-timeline (+1/-1/💬4)
  1 issues created:
  - Add a method to enumerate available types of entries (by spanicker)
    https://github.com/w3c/performance-timeline/issues/77

  2 issues received 4 new comments:
  - #77 Add a method to enumerate available types of entries (3 by igrigorik, spanicker)
    https://github.com/w3c/performance-timeline/issues/77
  - #56 Ability to observers past set of performance entries (1 by igrigorik)
    https://github.com/w3c/performance-timeline/issues/56

  1 issues closed:
  - Ability to observers past set of performance entries https://github.com/w3c/performance-timeline/issues/56

* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #58 ResourceTiming and preconnect (1 by bluesmoon)
    https://github.com/w3c/resource-timing/issues/58

* w3c/navigation-timing (+1/-0/💬4)
  1 issues created:
  - Obsolete partial interface to the Performance has incorrect exposure setting (by SaschaNaz)
    https://github.com/w3c/navigation-timing/issues/70

  1 issues received 4 new comments:
  - #70 Obsolete partial interface to the Performance has incorrect exposure setting (4 by igrigorik, plehegar, SaschaNaz)
    https://github.com/w3c/navigation-timing/issues/70

* w3c/beacon (+0/-1/💬1)
  1 issues received 1 new comments:
  - #43 Privacy & Security section not current (1 by igrigorik)
    https://github.com/w3c/beacon/issues/43

  1 issues closed:
  - maximum data size rules still seem ambiguous https://github.com/w3c/beacon/issues/42

* w3c/page-visibility (+1/-0/💬0)
  1 issues created:
  - onvisibilitychange is not implemented (by plehegar)
    https://github.com/w3c/page-visibility/issues/31

* w3c/preload (+2/-1/💬6)
  2 issues created:
  - Link element interface extensions (by annevk)
    https://github.com/w3c/preload/issues/95
  - Should the spec say something about the `request destination` of an HTTP/2 push? (by deweerdt)
    https://github.com/w3c/preload/issues/94

  2 issues received 6 new comments:
  - #94 Should the spec say something about the `request destination` of an HTTP/2 push? (5 by igrigorik, deweerdt, yoavweiss)
    https://github.com/w3c/preload/issues/94
  - #80 Require "as" attribute (1 by yoavweiss)
    https://github.com/w3c/preload/issues/80

  1 issues closed:
  - Should the spec say something about the `request destination` of an HTTP/2 push? https://github.com/w3c/preload/issues/94



Pull requests
-------------
* w3c/performance-timeline (+0/-1/💬2)
  1 pull requests received 2 new comments:
  - #76 `PerformanceObserverInit.buffered` and `add to performance entry buffer` flags (2 by igrigorik)
    https://github.com/w3c/performance-timeline/pull/76

  1 pull requests merged:
  - `PerformanceObserverInit.buffered` and `add to performance entry buffer` flags
    https://github.com/w3c/performance-timeline/pull/76

* w3c/navigation-timing (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #67 chore(.travis.yml): run link checker before publishing (1 by marcoscaceres)
    https://github.com/w3c/navigation-timing/pull/67

* w3c/beacon (+1/-0/💬2)
  1 pull requests submitted:
  - Update privacy & security section to reflect CORS processing logic. (by igrigorik)
    https://github.com/w3c/beacon/pull/44

  1 pull requests received 2 new comments:
  - #34 switch to whitelist for corsMode (2 by plehegar, bzbarsky)
    https://github.com/w3c/beacon/pull/34


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