Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬5)
  2 issues received 5 new comments:
  - #120 TFO and secureConnectionStart (3 by bluesmoon, nicjansma)
    https://github.com/w3c/resource-timing/issues/120
  - #129 Unusual RT timings in IE & Edge (2 by fshort, nicjansma)
    https://github.com/w3c/resource-timing/issues/129

* w3c/navigation-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #65 Please fix at least your broken links, if you want anyone to ever make any sense of your specs (1 by marcoscaceres)
    https://github.com/w3c/navigation-timing/issues/65

* w3c/device-memory (+1/-0/💬1)
  1 issues created:
  - Implementing this RFC is harmful (by KOLANICH)
    https://github.com/w3c/device-memory/issues/20

  1 issues received 1 new comments:
  - #20 Implementing this RFC is harmful (1 by detj)
    https://github.com/w3c/device-memory/issues/20

* w3c/paint-timing (+1/-0/💬5)
  1 issues created:
  - Eliminate "4.1. Modifications to other specifications" (by tdresser)
    https://github.com/w3c/paint-timing/issues/26

  1 issues received 5 new comments:
  - #14 Headings should be sentence case, not titlecase (5 by npm1, domenic)
    https://github.com/w3c/paint-timing/issues/14



Pull requests
-------------
* w3c/hr-time (+0/-0/💬2)
  2 pull requests received 2 new comments:
  - #53 Harmonized links and references, adding links to tests and issues (1 by plehegar)
    https://github.com/w3c/hr-time/pull/53
  - #54 Update spec to fix ambiguity around Time Origin definition. (1 by divmain)
    https://github.com/w3c/hr-time/pull/54

* w3c/performance-timeline (+0/-0/💬8)
  2 pull requests received 8 new comments:
  - #98 define PerformanceObserver#takeRecords() (5 by igrigorik, npm1)
    https://github.com/w3c/performance-timeline/pull/98
  - #97 Add takeRecords() to PerformanceObserver (3 by igrigorik, npm1)
    https://github.com/w3c/performance-timeline/pull/97

* w3c/user-timing (+0/-1/💬5)
  2 pull requests received 5 new comments:
  - #34 Editorial: clean up example a bit (4 by marcoscaceres, philipwalton, siusin)
    https://github.com/w3c/user-timing/pull/34
  - #30 Clarify that measure() may throw a SyntaxError (1 by philipwalton)
    https://github.com/w3c/user-timing/pull/30

  1 pull requests merged:
  - Editorial: clean up example a bit
    https://github.com/w3c/user-timing/pull/34

* w3c/device-memory (+0/-1/💬2)
  1 pull requests received 2 new comments:
  - #19 Add remark about lower/upper bounds changeability (2 by tomayac)
    https://github.com/w3c/device-memory/pull/19

  1 pull requests merged:
  - Add remark about lower/upper bounds changeability
    https://github.com/w3c/device-memory/pull/19

* w3c/paint-timing (+1/-0/💬1)
  1 pull requests submitted:
  - Fix nits in PerformancePaintTiming and headers (by npm1)
    https://github.com/w3c/paint-timing/pull/27

  1 pull requests received 1 new comments:
  - #27 Fix nits in PerformancePaintTiming and headers (1 by npm1)
    https://github.com/w3c/paint-timing/pull/27


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