Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #118 should redirected navigations have a workerStart value if a previous redirect URL was intercepted (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/118 [Clarification] [needs tests] [requires group agreement] 

* w3c/user-timing (+1/-0/💬7)
  1 issues created:
  - Allow marks and measures to be shown in developer tooling without adding it to the performance timeline (by anniesullie)
    https://github.com/w3c/user-timing/issues/68 

  1 issues received 7 new comments:
  - #68 Allow marks and measures to be shown in developer tooling without adding it to the performance timeline (7 by bgirard, npm1, rniwa, tdresser)
    https://github.com/w3c/user-timing/issues/68 

* w3c/page-visibility (+1/-0/💬0)
  1 issues created:
  - Lack of clarity on how occlusion behavior interacts with iframes (by kg)
    https://github.com/w3c/page-visibility/issues/56 

* w3c/server-timing (+1/-0/💬2)
  1 issues created:
  - Using Server-timing to carry TraceID (by plehegar)
    https://github.com/w3c/server-timing/issues/65 [question] 

  1 issues received 2 new comments:
  - #65 Using Server-timing to carry TraceID (2 by SergeyKanzhelev, yoavweiss)
    https://github.com/w3c/server-timing/issues/65 [question] 



Pull requests
-------------
* w3c/hr-time (+1/-0/💬0)
  1 pull requests submitted:
  - Prep for upcoming (by plehegar)
    https://github.com/w3c/hr-time/pull/85 [editorial] 

* w3c/requestidlecallback (+1/-1/💬3)
  1 pull requests submitted:
  - Define algorithm for determining whether high priority work exists. (by rmcilroy)
    https://github.com/w3c/requestidlecallback/pull/88 

  2 pull requests received 3 new comments:
  - #88 Define algorithm for determining whether high priority work exists. (2 by rmcilroy)
    https://github.com/w3c/requestidlecallback/pull/88 
  - #85 Avoid calling start an idle period directly now that the event loop does it (1 by rmcilroy)
    https://github.com/w3c/requestidlecallback/pull/85 

  1 pull requests merged:
  - Avoid calling start an idle period directly now that the event loop does it
    https://github.com/w3c/requestidlecallback/pull/85 


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