Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/user-timing (+0/-0/💬4)
  1 issues received 4 new comments:
  - #68 Allow marks and measures to be shown in developer tooling without adding it to the performance timeline (4 by anniesullie, bgirard, bvaughn, tdresser)
    https://github.com/w3c/user-timing/issues/68 

* w3c/requestidlecallback (+0/-0/💬1)
  1 issues received 1 new comments:
  - #82 The order of idle callbacks across windows is inconsistent between spec & UAs  (1 by rniwa)
    https://github.com/w3c/requestidlecallback/issues/82 

* w3c/longtasks (+3/-0/💬6)
  3 issues created:
  - "Not execute this loop" does not account for update the rendering (by annevk)
    https://github.com/w3c/longtasks/issues/77 
  - Event loop timing reporting seems to ignore reentrancy (by annevk)
    https://github.com/w3c/longtasks/issues/76 
  - Top-level browsing context scoping (by annevk)
    https://github.com/w3c/longtasks/issues/75 

  3 issues received 6 new comments:
  - #77 "Not execute this loop" does not account for update the rendering (2 by annevk, npm1)
    https://github.com/w3c/longtasks/issues/77 
  - #76 Event loop timing reporting seems to ignore reentrancy (2 by annevk, npm1)
    https://github.com/w3c/longtasks/issues/76 
  - #75 Top-level browsing context scoping (2 by annevk, npm1)
    https://github.com/w3c/longtasks/issues/75 

* w3c/server-timing (+1/-0/💬7)
  1 issues created:
  - Server Timing can be used a persistent 3rd party identifier (by JibberJim)
    https://github.com/w3c/server-timing/issues/67 

  1 issues received 7 new comments:
  - #67 Server Timing can be used a persistent 3rd party identifier (7 by JibberJim, bripkens, yoavweiss)
    https://github.com/w3c/server-timing/issues/67 



Pull requests
-------------
* w3c/hr-time (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #85 Prep for upcoming (1 by plehegar)
    https://github.com/w3c/hr-time/pull/85 [editorial] 

  1 pull requests merged:
  - Prep for upcoming
    https://github.com/w3c/hr-time/pull/85 [editorial] 

* w3c/resource-timing (+2/-0/💬1)
  2 pull requests submitted:
  - Update timing allow check algorithm (by npm1)
    https://github.com/w3c/resource-timing/pull/218 
  - Protect workerStart with a TAO check (by yoavweiss)
    https://github.com/w3c/resource-timing/pull/217 

  1 pull requests received 1 new comments:
  - #217 Protect workerStart with a TAO check (1 by yoavweiss)
    https://github.com/w3c/resource-timing/pull/217 

* w3c/beacon (+1/-0/💬0)
  1 pull requests submitted:
  - Add conformance section (by tidoust)
    https://github.com/w3c/beacon/pull/65 

* w3c/longtasks (+2/-2/💬0)
  2 pull requests submitted:
  - Update spec with buffered flag (by npm1)
    https://github.com/w3c/longtasks/pull/74 
  - Update explainer with buffered flag support (by npm1)
    https://github.com/w3c/longtasks/pull/73 

  2 pull requests merged:
  - Update spec with buffered flag
    https://github.com/w3c/longtasks/pull/74 
  - Update explainer with buffered flag support
    https://github.com/w3c/longtasks/pull/73 

* w3c/server-timing (+1/-0/💬0)
  1 pull requests submitted:
  - Add conformance section (by tidoust)
    https://github.com/w3c/server-timing/pull/66 


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