Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+1/-0/💬2)
  1 issues created:
  - resource timing buffer full flag should be set to true before firing resourcetimingbufferfull event (by rniwa)
    https://github.com/w3c/resource-timing/issues/134

  1 issues received 2 new comments:
  - #133 Resource processing time (2 by tdresser, nicjansma)
    https://github.com/w3c/resource-timing/issues/133

* w3c/navigation-timing (+0/-3/💬7)
  4 issues received 7 new comments:
  - #79 Timings for beforeUnload event (3 by igrigorik, andydavies)
    https://github.com/w3c/navigation-timing/issues/79
  - #65 Please fix at least your broken links, if you want anyone to ever make any sense of your specs (2 by igrigorik, marcoscaceres)
    https://github.com/w3c/navigation-timing/issues/65
  - #81 Navigation Timing should be exposed in the Worker context (1 by igrigorik)
    https://github.com/w3c/navigation-timing/issues/81
  - #78 Should processing model cut the steps defined by PerformanceResourceTiming? (1 by igrigorik)
    https://github.com/w3c/navigation-timing/issues/78

  3 issues closed:
  - IDL should xref PerformanceResourceTiming https://github.com/w3c/navigation-timing/issues/64
  - Navigation Timing should be exposed in the Worker context https://github.com/w3c/navigation-timing/issues/81
  - Timings for beforeUnload event https://github.com/w3c/navigation-timing/issues/79

* w3c/user-timing (+0/-0/💬4)
  2 issues received 4 new comments:
  - #22 What does "navigationStart" mean as a second argument to performance.measure() in a web worker? (3 by tdresser, philipwalton)
    https://github.com/w3c/user-timing/issues/22
  - #21 measure() may throw SyntaxError (1 by philipwalton)
    https://github.com/w3c/user-timing/issues/21

* w3c/server-timing (+2/-0/💬3)
  2 issues created:
  - clarify invalid params (by cvazac)
    https://github.com/w3c/server-timing/issues/48
  - clarify incomplete params (by cvazac)
    https://github.com/w3c/server-timing/issues/46

  1 issues received 3 new comments:
  - #46 clarify incomplete params (3 by KershawChang, cvazac, yoavweiss)
    https://github.com/w3c/server-timing/issues/46



Pull requests
-------------
* w3c/hr-time (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #53 Harmonized links and references, adding links to tests and issues (1 by marcoscaceres)
    https://github.com/w3c/hr-time/pull/53

* w3c/user-timing (+1/-0/💬1)
  1 pull requests submitted:
  - Address outstanding L2 issues (by philipwalton)
    https://github.com/w3c/user-timing/pull/35

  1 pull requests received 1 new comments:
  - #30 Clarify that measure() may throw a SyntaxError (1 by philipwalton)
    https://github.com/w3c/user-timing/pull/30

* w3c/server-timing (+1/-1/💬3)
  1 pull requests submitted:
  - clarify duplicate param names (by cvazac)
    https://github.com/w3c/server-timing/pull/47

  1 pull requests received 3 new comments:
  - #47 clarify duplicate param names (3 by ddragana, cvazac)
    https://github.com/w3c/server-timing/pull/47

  1 pull requests merged:
  - clarify duplicate param names
    https://github.com/w3c/server-timing/pull/47


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