Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+3/-0/💬7)
  3 issues created:
  - Make high resolution time dependant on cross-origin isolated (by annevk)
    https://github.com/w3c/hr-time/issues/89 
  - High resolution time is not defined (by annevk)
    https://github.com/w3c/hr-time/issues/88 
  - Provide hook for getting a high resolution time between time origin and a "time" (by annevk)
    https://github.com/w3c/hr-time/issues/87 

  2 issues received 7 new comments:
  - #89 Make high resolution time dependant on cross-origin isolated (4 by mikewest, npm1, yoavweiss)
    https://github.com/w3c/hr-time/issues/89 
  - #79 Security and privacy considerations for DOMHighResTimeStamp resolution (3 by annevk, pes10k)
    https://github.com/w3c/hr-time/issues/79 [privacy-tracker] [security-tracker] 

* w3c/performance-timeline (+1/-1/💬1)
  1 issues created:
  - performance.timing obsoleted: What should web developers use instead? (by sideshowbarker)
    https://github.com/w3c/performance-timeline/issues/165 

  1 issues received 1 new comments:
  - #163 Use of "SyntaxError" seems incorrect, should be TypeError (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/163 

  1 issues closed:
  - Use of "SyntaxError" seems incorrect, should be TypeError https://github.com/w3c/performance-timeline/issues/163 

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

* w3c/longtasks (+1/-1/💬6)
  1 issues created:
  - Attribution for alert() or other tasks blocked by user input (by npm1)
    https://github.com/w3c/longtasks/issues/83 

  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-discussion] 
  - #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 (3 by annevk, nicjansma, yoavweiss)
    https://github.com/w3c/longtasks/issues/75 [requires-work] 

  1 issues closed:
  - Event loop timing reporting seems to ignore reentrancy https://github.com/w3c/longtasks/issues/76 [requires-discussion] 

* w3c/server-timing (+1/-0/💬0)
  1 issues created:
  - API for fetching other metadata (by hauleth)
    https://github.com/w3c/server-timing/issues/72 



Pull requests
-------------
* w3c/performance-timeline (+1/-1/💬0)
  1 pull requests submitted:
  - Do not use SyntaxError (by npm1)
    https://github.com/w3c/performance-timeline/pull/164 

  1 pull requests merged:
  - Do not use SyntaxError
    https://github.com/w3c/performance-timeline/pull/164 

* w3c/device-memory (+1/-1/💬2)
  1 pull requests submitted:
  - New deploy key (by yoavweiss)
    https://github.com/w3c/device-memory/pull/30 

  1 pull requests received 2 new comments:
  - #30 New deploy key (2 by yoavweiss)
    https://github.com/w3c/device-memory/pull/30 

  1 pull requests merged:
  - New deploy key
    https://github.com/w3c/device-memory/pull/30 


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