Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-0/💬1)
  1 issues received 1 new comments:
  - #88 High resolution time is not defined (1 by mmocny)
    https://github.com/w3c/hr-time/issues/88 

* w3c/performance-timeline (+0/-2/💬7)
  3 issues received 7 new comments:
  - #165 performance.timing obsoleted: What should web developers use instead? (4 by npm1, sideshowbarker, yoavweiss)
    https://github.com/w3c/performance-timeline/issues/165 
  - #162 Queue the entry should require a global object as input (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/162 
  - #100 Ensure tests are clean (2 by yoavweiss)
    https://github.com/w3c/performance-timeline/issues/100 

  2 issues closed:
  - performance.timing obsoleted: What should web developers use instead? https://github.com/w3c/performance-timeline/issues/165 
  - Queue the entry should require a global object as input https://github.com/w3c/performance-timeline/issues/162 

* w3c/navigation-timing (+1/-1/💬1)
  1 issues created:
  - Respec errors (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/127 

  1 issues received 1 new comments:
  - #127 Respec errors (1 by marcoscaceres)
    https://github.com/w3c/navigation-timing/issues/127 

  1 issues closed:
  - Respec errors https://github.com/w3c/navigation-timing/issues/127 

* w3c/user-timing (+1/-1/💬0)
  1 issues created:
  - Respec errors (by yoavweiss)
    https://github.com/w3c/user-timing/issues/71 

  1 issues closed:
  - Respec errors https://github.com/w3c/user-timing/issues/71 

* w3c/page-visibility (+1/-1/💬1)
  1 issues created:
  - Respec errors (by yoavweiss)
    https://github.com/w3c/page-visibility/issues/60 

  1 issues received 1 new comments:
  - #60 Respec errors (1 by marcoscaceres)
    https://github.com/w3c/page-visibility/issues/60 

  1 issues closed:
  - Respec errors https://github.com/w3c/page-visibility/issues/60 

* w3c/device-memory (+1/-0/💬1)
  1 issues created:
  - Setup auto-publishing (by yoavweiss)
    https://github.com/w3c/device-memory/issues/31 

  1 issues received 1 new comments:
  - #26 Deploy failed on later push to master (1 by yoavweiss)
    https://github.com/w3c/device-memory/issues/26 

* w3c/paint-timing (+1/-1/💬3)
  1 issues created:
  - Set up auto-publishing? (by yoavweiss)
    https://github.com/w3c/paint-timing/issues/87 

  2 issues received 3 new comments:
  - #87 Set up auto-publishing? (2 by mmocny, npm1)
    https://github.com/w3c/paint-timing/issues/87 
  - #31 What is the scope of timings? (1 by yoavweiss)
    https://github.com/w3c/paint-timing/issues/31 [duplicate] 

  1 issues closed:
  - What is the scope of timings? https://github.com/w3c/paint-timing/issues/31 [duplicate] 

* w3c/longtasks (+1/-2/💬6)
  1 issues created:
  - Privacy & Security mitigations should not be in an external document (by yoavweiss)
    https://github.com/w3c/longtasks/issues/85 

  3 issues received 6 new comments:
  - #80 Combination of paint timing and long tasks can expose precise paint timing (1 by npm1)
    https://github.com/w3c/longtasks/issues/80 [requires-work] 
  - #76 Event loop timing reporting seems to ignore reentrancy (1 by mmocny)
    https://github.com/w3c/longtasks/issues/76 
  - #75 Top-level browsing context scoping (4 by annevk, domenic, npm1)
    https://github.com/w3c/longtasks/issues/75 [requires-discussion] [requires-work] 

  2 issues closed:
  - Top-level browsing context scoping https://github.com/w3c/longtasks/issues/75 [requires-discussion] [requires-work] 
  - Combination of paint timing and long tasks can expose precise paint timing https://github.com/w3c/longtasks/issues/80 [requires-work] 

* w3c/server-timing (+1/-1/💬2)
  1 issues created:
  - Respec errors (by yoavweiss)
    https://github.com/w3c/server-timing/issues/73 

  1 issues received 2 new comments:
  - #73 Respec errors (2 by sidvishnoi, yoavweiss)
    https://github.com/w3c/server-timing/issues/73 

  1 issues closed:
  - Respec errors https://github.com/w3c/server-timing/issues/73 



Pull requests
-------------
* w3c/user-timing (+1/-1/💬0)
  1 pull requests submitted:
  - Editorial: xref fixes (by marcoscaceres)
    https://github.com/w3c/user-timing/pull/72 

  1 pull requests merged:
  - Editorial: xref fixes
    https://github.com/w3c/user-timing/pull/72 

* w3c/paint-timing (+2/-2/💬0)
  2 pull requests submitted:
  - Update affiliation for NoamR (by noamr)
    https://github.com/w3c/paint-timing/pull/86 
  - Update Editors (by npm1)
    https://github.com/w3c/paint-timing/pull/85 

  2 pull requests merged:
  - Update Editors
    https://github.com/w3c/paint-timing/pull/85 
  - Update affiliation for NoamR
    https://github.com/w3c/paint-timing/pull/86 

* w3c/longtasks (+1/-1/💬1)
  1 pull requests submitted:
  - Refactor report long task (by npm1)
    https://github.com/w3c/longtasks/pull/84 

  1 pull requests received 1 new comments:
  - #84 Refactor report long task (1 by npm1)
    https://github.com/w3c/longtasks/pull/84 

  1 pull requests merged:
  - Refactor report long task
    https://github.com/w3c/longtasks/pull/84 

* w3c/server-timing (+1/-1/💬0)
  1 pull requests submitted:
  - chore: fix ReSpec linking error  (by sidvishnoi)
    https://github.com/w3c/server-timing/pull/74 

  1 pull requests merged:
  - chore: fix ReSpec linking error 
    https://github.com/w3c/server-timing/pull/74 


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