Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/performance-timeline (+0/-0/💬1)
  1 issues received 1 new comments:
  - #160 Using a single observer instance throughout the application lifetime (1 by yoavweiss)
    https://github.com/w3c/performance-timeline/issues/160 

* w3c/resource-timing (+3/-0/💬16)
  3 issues created:
  - Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent accidental application state leakage (by kdzwinel)
    https://github.com/w3c/resource-timing/issues/223 
  - Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage (by kdzwinel)
    https://github.com/w3c/resource-timing/issues/222 
  - Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy (by kdzwinel)
    https://github.com/w3c/resource-timing/issues/221 

  3 issues received 16 new comments:
  - #222 Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage (12 by snyderp, yoavweiss)
    https://github.com/w3c/resource-timing/issues/222 [privacy-tracker] 
  - #221 Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy (3 by snyderp, yoavweiss)
    https://github.com/w3c/resource-timing/issues/221 [privacy-tracker] 
  - #210 Cross-origin IFRAME opting-in to sharing ResourceTiming data (1 by nicjansma)
    https://github.com/w3c/resource-timing/issues/210 

* w3c/page-visibility (+0/-1/💬1)
  1 issues received 1 new comments:
  - #56 Lack of clarity on how occlusion behavior interacts with iframes (1 by yoavweiss)
    https://github.com/w3c/page-visibility/issues/56 [enhancement] 

  1 issues closed:
  - Lack of clarity on how occlusion behavior interacts with iframes https://github.com/w3c/page-visibility/issues/56 [enhancement] 

* w3c/device-memory (+1/-0/💬0)
  1 issues created:
  - Deploy failed on later push to master (by foolip)
    https://github.com/w3c/device-memory/issues/26 



Pull requests
-------------
* w3c/resource-timing (+1/-0/💬0)
  1 pull requests submitted:
  - TAO Protect nextHopProtocol (by yoavweiss)
    https://github.com/w3c/resource-timing/pull/224 

* w3c/device-memory (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #25 Convert NavigatorDeviceClass to an interface mixin (1 by foolip)
    https://github.com/w3c/device-memory/pull/25 


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