Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-1/💬1)
  1 issues received 1 new comments:
  - #56 Reducing the precision of the DOMHighResTimeStamp resolution (1 by yoavweiss)
    https://github.com/w3c/hr-time/issues/56 [security] 

  1 issues closed:
  - Reducing the precision of the DOMHighResTimeStamp resolution https://github.com/w3c/hr-time/issues/56 [security] 

* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #96 Clarify behavior of setResourceTimingBufferSize (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/96 [discuss_280618] [test:missing-coverage] 

* w3c/navigation-timing (+2/-0/💬13)
  2 issues created:
  - Should navigationEntry's navigationType be updated according to the parent page ? (by shacharz)
    https://github.com/w3c/navigation-timing/issues/85 
  - secureConnectionStart definition is inconsistent with ResourceTiming (by npm1)
    https://github.com/w3c/navigation-timing/issues/84 

  4 issues received 13 new comments:
  - #85 Should navigationEntry's navigationType be updated according to the parent page ? (7 by shacharz, igrigorik, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/85 [test:missing-coverage] 
  - #65 Please fix at least your broken links, if you want anyone to ever make any sense of your specs (3 by igrigorik, yoavweiss, bzbarsky)
    https://github.com/w3c/navigation-timing/issues/65 
  - #78 Should processing model cut the steps defined by PerformanceResourceTiming? (2 by igrigorik, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/78 
  - #84 secureConnectionStart definition is inconsistent with ResourceTiming (1 by toddreifsteck)
    https://github.com/w3c/navigation-timing/issues/84 

* w3c/page-visibility (+1/-1/💬4)
  1 issues created:
  - Provide a clear way to hook into "document becomes visible/hidden" (by siusin)
    https://github.com/w3c/page-visibility/issues/40 

  2 issues received 4 new comments:
  - #37 typo: "5.3 onvisiblitychange event handler" (3 by yoavweiss, siusin)
    https://github.com/w3c/page-visibility/issues/37 
  - #39 Why does visibilitychange fire after pagehide in the unload flow? (1 by spanicker)
    https://github.com/w3c/page-visibility/issues/39 

  1 issues closed:
  - typo: "5.3 onvisiblitychange event handler" https://github.com/w3c/page-visibility/issues/37 

* w3c/preload (+1/-0/💬7)
  1 issues created:
  - spec shuold mention that relList must also be implemented if preload is implemented (by safareli)
    https://github.com/w3c/preload/issues/126 

  1 issues received 7 new comments:
  - #7 how to feature detect? (7 by safareli, getify, yoavweiss)
    https://github.com/w3c/preload/issues/7 

* w3c/resource-hints (+0/-0/💬1)
  1 issues received 1 new comments:
  - #72 Hinting HTTP Alternative Services (1 by LPardue)
    https://github.com/w3c/resource-hints/issues/72 

* w3c/longtasks (+1/-0/💬0)
  1 issues created:
  - Can we get call stack ? (by kshyju)
    https://github.com/w3c/longtasks/issues/42 

* w3c/server-timing (+1/-0/💬2)
  1 issues created:
  - Relax (or remove) trailer processing requirement (by igrigorik)
    https://github.com/w3c/server-timing/issues/58 

  1 issues received 2 new comments:
  - #58 Relax (or remove) trailer processing requirement (2 by igrigorik, cvazac)
    https://github.com/w3c/server-timing/issues/58 




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