Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-3/💬5)
  4 issues received 5 new comments:
  - #303 Reflect preload information (in ResourceTiming?) (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/303 
  - #252 4.6 Integrate the processing model with Fetch (2 by noamr, yoavweiss)
    https://github.com/w3c/resource-timing/issues/252 [fetch-integration] 
  - #228 Timing-Allow-Origin may expose allowed URLs (1 by noamr)
    https://github.com/w3c/resource-timing/issues/228 [Clarification] 
  - #200 Be a bit more explicit about which subresources are to be ignored from stylesheets (1 by noamr)
    https://github.com/w3c/resource-timing/issues/200 [Clarification] [requires Fetch integration] 

  3 issues closed:
  - 4.6 Integrate the processing model with Fetch https://github.com/w3c/resource-timing/issues/252 [fetch-integration] 
  - Timing-Allow-Origin may expose allowed URLs https://github.com/w3c/resource-timing/issues/228 [Clarification] 
  - Be a bit more explicit about which subresources are to be ignored from stylesheets https://github.com/w3c/resource-timing/issues/200 [Clarification] [requires Fetch integration] 

* w3c/navigation-timing (+0/-2/💬1)
  1 issues received 1 new comments:
  - #148 Add a test that ensures `fetchStart` matches the SW's fetch event start time (1 by noamr)
    https://github.com/w3c/navigation-timing/issues/148 

  2 issues closed:
  - 4.1 Processing model should rely on Fetch/HTML https://github.com/w3c/navigation-timing/issues/136 [fetch-integration] 
  - Add a test that ensures `fetchStart` matches the SW's fetch event start time https://github.com/w3c/navigation-timing/issues/148 

* w3c/page-visibility (+0/-1/💬2)
  2 issues received 2 new comments:
  - #74 Maybe we should fold this spec into HTML? (1 by marcoscaceres)
    https://github.com/w3c/page-visibility/issues/74 
  - #51 HTML spec should call visibilitychange algorithms directly. (1 by noamr)
    https://github.com/w3c/page-visibility/issues/51 

  1 issues closed:
  - HTML spec should call visibilitychange algorithms directly. https://github.com/w3c/page-visibility/issues/51 



Pull requests
-------------
* w3c/hr-time (+0/-0/💬10)
  1 pull requests received 10 new comments:
  - #130 Expose everywhere (10 by marcoscaceres, saschanaz, sidvishnoi)
    https://github.com/w3c/hr-time/pull/130 


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config