Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-3/💬3)
  2 issues received 3 new comments:
  - #96 Comments on "Define 'relative high resolution time'" (2 by annevk, yoavweiss)
    https://github.com/w3c/hr-time/issues/96 
  - #88 High resolution time is not defined (1 by yoavweiss)
    https://github.com/w3c/hr-time/issues/88 [editorial] [enhancement] [hackathon_15_09_20] [hackathon_2020] 

  3 issues closed:
  - Comments on "Define 'relative high resolution time'" https://github.com/w3c/hr-time/issues/96 
  - High resolution time is not defined https://github.com/w3c/hr-time/issues/88 [editorial] [enhancement] [hackathon_15_09_20] [hackathon_2020] 
  - Expose "unsafe now" for internal uses https://github.com/w3c/hr-time/issues/99 

* w3c/performance-timeline (+0/-0/💬3)
  2 issues received 3 new comments:
  - #100 Ensure tests are clean (2 by sefeng211, yoavweiss)
    https://github.com/w3c/performance-timeline/issues/100 
  - #85 Would like a precise way to map PerformanceTimings to FetchEvent (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/85 [enhancement] 

* w3c/resource-timing (+3/-1/💬16)
  3 issues created:
  - Current definition of `startTime` exposes total redirect time even when TAO fails (by noamr)
    https://github.com/w3c/resource-timing/issues/260 
  - Would like a precise way to map PerformanceTimings to FetchEvent (by jakearchibald)
    https://github.com/w3c/resource-timing/issues/259 
  - Which DNS timings should be exposed when fetching redirected resource (by tommckee1)
    https://github.com/w3c/resource-timing/issues/258 

  4 issues received 16 new comments:
  - #260 Current definition of `startTime` exposes total redirect time even when TAO fails (4 by noamr, npm1)
    https://github.com/w3c/resource-timing/issues/260 
  - #259 Would like a precise way to map PerformanceTimings to FetchEvent (1 by annevk)
    https://github.com/w3c/resource-timing/issues/259 
  - #258 Which DNS timings should be exposed when fetching redirected resource (5 by npm1, tommckee1, yoavweiss)
    https://github.com/w3c/resource-timing/issues/258 
  - #200 Be a bit more explicit about which subresources are to be ignored from stylesheets (6 by annevk, mfalken, yoavweiss)
    https://github.com/w3c/resource-timing/issues/200 [Clarification] [requires Fetch integration] 

  1 issues closed:
  - Which DNS timings should be exposed when fetching redirected resource https://github.com/w3c/resource-timing/issues/258 

* w3c/page-visibility (+0/-0/💬1)
  1 issues received 1 new comments:
  - #65 Republish spec (1 by yoavweiss)
    https://github.com/w3c/page-visibility/issues/65 



Pull requests
-------------
* w3c/hr-time (+4/-4/💬5)
  4 pull requests submitted:
  - Change editors (by yoavweiss)
    https://github.com/w3c/hr-time/pull/110 
  - Fix reference to unsafe shared time (by yoavweiss)
    https://github.com/w3c/hr-time/pull/109 
  - Fix links to shared monotonic clock (by noamr)
    https://github.com/w3c/hr-time/pull/108 
  - Change "global monotonic clock" to "universal" (by noamr)
    https://github.com/w3c/hr-time/pull/107 

  2 pull requests received 5 new comments:
  - #107 Change "global monotonic clock" to "shared" and expose new algorithm "unsafe shared current time" (4 by noamr, yoavweiss)
    https://github.com/w3c/hr-time/pull/107 
  - #106 Coarsen timeOrigin (1 by yoavweiss)
    https://github.com/w3c/hr-time/pull/106 

  4 pull requests merged:
  - Change editors
    https://github.com/w3c/hr-time/pull/110 
  - Fix reference to unsafe shared time
    https://github.com/w3c/hr-time/pull/109 
  - Fix links to shared monotonic clock
    https://github.com/w3c/hr-time/pull/108 
  - Change "global monotonic clock" to "shared" and expose new algorithm "unsafe shared current time"
    https://github.com/w3c/hr-time/pull/107 

* w3c/performance-timeline (+1/-1/💬0)
  1 pull requests submitted:
  - Change editors (by yoavweiss)
    https://github.com/w3c/performance-timeline/pull/179 

  1 pull requests merged:
  - Change editors
    https://github.com/w3c/performance-timeline/pull/179 

* w3c/resource-timing (+0/-0/💬2)
  1 pull requests received 2 new comments:
  - #224 TAO-Protect nextHopProtocol (2 by noamr, yoavweiss)
    https://github.com/w3c/resource-timing/pull/224 

* w3c/navigation-timing (+1/-1/💬2)
  1 pull requests submitted:
  - Change editors (by yoavweiss)
    https://github.com/w3c/navigation-timing/pull/139 

  1 pull requests received 2 new comments:
  - #131 workerStart and redirects (2 by nicjansma)
    https://github.com/w3c/navigation-timing/pull/131 [hackathon_15_09_20] [hackathon_2020] 

  1 pull requests merged:
  - Change editors
    https://github.com/w3c/navigation-timing/pull/139 

* w3c/user-timing (+2/-2/💬2)
  2 pull requests submitted:
  - Remove DOS newlines (by yoavweiss)
    https://github.com/w3c/user-timing/pull/79 
  - Change editors (by yoavweiss)
    https://github.com/w3c/user-timing/pull/78 

  1 pull requests received 2 new comments:
  - #78 Change editors (2 by yoavweiss)
    https://github.com/w3c/user-timing/pull/78 

  2 pull requests merged:
  - Change editors
    https://github.com/w3c/user-timing/pull/78 
  - Remove DOS newlines
    https://github.com/w3c/user-timing/pull/79 


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