Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-5/💬5)
  3 issues received 5 new comments:
  - #173 Clarify cross-origin resources (2 by alanwaketan)
    https://github.com/w3c/resource-timing/issues/173 [requires Fetch integration] 
  - #118 should redirected navigations have a workerStart value if a previous redirect URL was intercepted (2 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/118 [Clarification] [needs tests] [requires group agreement] 
  - #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (1 by igrigorik)
    https://github.com/w3c/resource-timing/issues/119 [Clarification] [needs tests] [requires Fetch integration] 

  5 issues closed:
  - should redirected navigations have a workerStart value if a previous redirect URL was intercepted https://github.com/w3c/resource-timing/issues/118 [Clarification] [needs tests] [requires group agreement] 
  - DNS lookups can occur even when reusing a connection https://github.com/w3c/resource-timing/issues/160 [Pending PR] 
  - Navigation Preload can have negative times https://github.com/w3c/resource-timing/issues/139 [Pending PR] 
  - TFO and secureConnectionStart https://github.com/w3c/resource-timing/issues/120 [Pending PR] 
  - How do dns and connectStart handle multiple ip/name options? https://github.com/w3c/resource-timing/issues/123 [Pending PR] 

* w3c/navigation-timing (+2/-0/💬0)
  2 issues created:
  - workerStart should be clearly defined as applicable to the last SW (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/100 
  - workerStart should be gated on timing-allow check (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/99 

* w3c/page-visibility (+1/-0/💬0)
  1 issues created:
  - visibilityState should say which top-level browsing context (by jyasskin)
    https://github.com/w3c/page-visibility/issues/41 

* w3c/preload (+0/-1/💬1)
  1 issues received 1 new comments:
  - #132 Question: What is the correct way to create ranges for media attributes? (1 by yoavweiss)
    https://github.com/w3c/preload/issues/132 

  1 issues closed:
  - Question: What is the correct way to create ranges for media attributes? https://github.com/w3c/preload/issues/132 

* w3c/requestidlecallback (+0/-0/💬2)
  1 issues received 2 new comments:
  - #71 "deadline" in the "start an idle period algorithm" should be defined in terms of event loop (2 by rniwa, yoavweiss)
    https://github.com/w3c/requestidlecallback/issues/71 



Pull requests
-------------
* w3c/resource-timing (+0/-4/💬4)
  3 pull requests received 4 new comments:
  - #189 Clarify that connectStart/connectEnd refer to the latest connection retry (2 by yoavweiss, toddreifsteck)
    https://github.com/w3c/resource-timing/pull/189 
  - #183 Add a note regarding negative timestamps for navigation preload requests (1 by yoavweiss)
    https://github.com/w3c/resource-timing/pull/183 
  - #187 Address the request retry case, and add a note (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/pull/187 

  4 pull requests merged:
  - Connection reuse does not imply DNS was not required
    https://github.com/w3c/resource-timing/pull/185 
  - Add a note regarding negative timestamps for navigation preload requests
    https://github.com/w3c/resource-timing/pull/183 
  - Address the request retry case, and add a note
    https://github.com/w3c/resource-timing/pull/187 
  - Clarify that connectStart/connectEnd refer to the latest connection retry
    https://github.com/w3c/resource-timing/pull/189 

* w3c/preload (+0/-0/💬3)
  1 pull requests received 3 new comments:
  - #134 imagesrcset and imagesizes mutations are appropriate times to obtain the resource (3 by domfarolino, yoavweiss)
    https://github.com/w3c/preload/pull/134 [requires group discussion] 


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