Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬2)
  1 issues received 2 new comments:
  - #204 Add tests for not-same-site nested contexts (2 by tommckee1, yoavweiss)
    https://github.com/w3c/resource-timing/issues/204 [test:missing-coverage] 

* w3c/navigation-timing (+1/-0/💬10)
  1 issues created:
  - Should pages with different COOP be able to get unload event start/end. (by hemeryar)
    https://github.com/w3c/navigation-timing/issues/169 

  4 issues received 10 new comments:
  - #163 How should prefetch be exposed? (3 by igrigorik, jeremyroman, sefeng211)
    https://github.com/w3c/navigation-timing/issues/163 
  - #154 Lack of Feature Parity with Performace.measure() in Level 2 (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/154 
  - #146 A scenario where transferSize is 0 for non cached loads (or may be not) (2 by noamr, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/146 
  - #140 AppCache meaning (4 by noamr, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/140 

* w3c/preload (+0/-0/💬1)
  1 issues received 1 new comments:
  - #127 Preload and SRI (1 by mushu999)
    https://github.com/w3c/preload/issues/127 [discuss] 

* w3c/server-timing (+0/-1/💬4)
  1 issues received 4 new comments:
  - #79 Clarify security context for PerformanceResourceTiming (4 by fred-wang, yoavweiss)
    https://github.com/w3c/server-timing/issues/79 [definition] 

  1 issues closed:
  - Clarify security context for PerformanceResourceTiming https://github.com/w3c/server-timing/issues/79 [definition] 



Pull requests
-------------
* w3c/resource-timing (+0/-0/💬2)
  1 pull requests received 2 new comments:
  - #302 Expose everywhere (2 by yoavweiss)
    https://github.com/w3c/resource-timing/pull/302 

* w3c/navigation-timing (+1/-1/💬4)
  1 pull requests submitted:
  - Hide redirectStart and redirectEnd for navigations with cross-origin redirects (by noamr)
    https://github.com/w3c/navigation-timing/pull/170 

  2 pull requests received 4 new comments:
  - #161 Add a landing attribute to PerformanceNavigationTiming (3 by jakearchibald, marcelduran, yoavweiss)
    https://github.com/w3c/navigation-timing/pull/161 
  - #131 workerStart and redirects (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/pull/131 [hackathon_15_09_20] [hackathon_2020] 

  1 pull requests merged:
  - Fix typo in markup
    https://github.com/w3c/navigation-timing/pull/162 

* w3c/requestidlecallback (+0/-0/💬3)
  3 pull requests received 3 new comments:
  - #98 Editorial: Use the HTML spec's timers infrastructure for `timeout` (1 by yoavweiss)
    https://github.com/w3c/requestidlecallback/pull/98 
  - #88 Define algorithm for determining whether high priority work exists. (1 by yoavweiss)
    https://github.com/w3c/requestidlecallback/pull/88 
  - #78 Better define deadline (1 by yoavweiss)
    https://github.com/w3c/requestidlecallback/pull/78 


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