Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+1/-2/💬9)
  1 issues created:
  - Comments on "Define 'relative high resolution time'" (by annevk)
    https://github.com/w3c/hr-time/issues/96 

  1 issues received 9 new comments:
  - #96 Comments on "Define 'relative high resolution time'" (9 by annevk, igneel64, npm1, yoavweiss)
    https://github.com/w3c/hr-time/issues/96 

  2 issues closed:
  - Comments on "Define 'relative high resolution time'" https://github.com/w3c/hr-time/issues/96 
  - Provide hook for getting a high resolution time between time origin and a "time" https://github.com/w3c/hr-time/issues/87 [editorial] [enhancement] [hackathon_15_09_20] 

* w3c/performance-timeline (+1/-0/💬2)
  1 issues created:
  - Hard to feature-detect observe() parameters (by npm1)
    https://github.com/w3c/performance-timeline/issues/176 

  1 issues received 2 new comments:
  - #168 Reset the observers (2 by npm1, wycats)
    https://github.com/w3c/performance-timeline/issues/168 

* w3c/resource-timing (+0/-0/💬7)
  4 issues received 7 new comments:
  - #220 Provide a TAO-bypass for Navigation timing (1 by caribouW3)
    https://github.com/w3c/resource-timing/issues/220 [editorial] [hackathon_15_09_20] 
  - #215 The step to queue a task to run fire a buffer full event should specify its source (1 by rniwa)
    https://github.com/w3c/resource-timing/issues/215 [hackathon_15_09_20] 
  - #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (4 by jakearchibald, makotoshimazu, mfalken)
    https://github.com/w3c/resource-timing/issues/119 [Clarification] [needs tests] [requires Fetch integration] 
  - #58 ResourceTiming and preconnect (1 by mhofman)
    https://github.com/w3c/resource-timing/issues/58 [whiteboard] 

* w3c/navigation-timing (+0/-0/💬3)
  3 issues received 3 new comments:
  - #128 worker start needs to be added to diagram (1 by nicjansma)
    https://github.com/w3c/navigation-timing/issues/128 [hackathon_15_09_20] 
  - #100 workerStart should be clearly defined as applicable to the last SW (1 by nicjansma)
    https://github.com/w3c/navigation-timing/issues/100 [WPT] [needs tests] 
  - #99 workerStart should be gated on same-origin check (1 by nicjansma)
    https://github.com/w3c/navigation-timing/issues/99 [WPT] [needs tests] 

* w3c/user-timing (+1/-1/💬0)
  1 issues created:
  - Clarify behavior when `detail` is omitted from `PerformanceMeasureOptions`  (by samweinig)
    https://github.com/w3c/user-timing/issues/74 

  1 issues closed:
  - Clarify behavior when `detail` is omitted from `PerformanceMeasureOptions`  https://github.com/w3c/user-timing/issues/74 

* w3c/longtasks (+0/-1/💬1)
  1 issues received 1 new comments:
  - #41 Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? (1 by npm1)
    https://github.com/w3c/longtasks/issues/41 [requires-discussion] 

  1 issues closed:
  - Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? https://github.com/w3c/longtasks/issues/41 [requires-discussion] 



Pull requests
-------------
* w3c/hr-time (+1/-2/💬15)
  1 pull requests submitted:
  - Correct algorithm definition & 'current high resolution time' reform - Fixes #96 (by igneel64)
    https://github.com/w3c/hr-time/pull/97 

  4 pull requests received 15 new comments:
  - #97 Correct algorithm definition & 'current high resolution time' reform - Fixes #96 (6 by annevk, yoavweiss)
    https://github.com/w3c/hr-time/pull/97 
  - #95 Define 'relative high resolution time' (1 by yoavweiss)
    https://github.com/w3c/hr-time/pull/95 
  - #94 Add a <dfn> for "high resolution time" (6 by annevk, mmocny, yoavweiss)
    https://github.com/w3c/hr-time/pull/94 [hackathon_15_09_20] 
  - #93 Limit the timer resolution in non-isolated contexts (2 by annevk, yoavweiss)
    https://github.com/w3c/hr-time/pull/93 [hackathon_15_09_20] 

  2 pull requests merged:
  - Correct algorithm definition & 'current high resolution time' reform - Fixes #96
    https://github.com/w3c/hr-time/pull/97 
  - Define 'relative high resolution time'
    https://github.com/w3c/hr-time/pull/95 [hackathon_15_09_20] 

* w3c/resource-timing (+0/-1/💬2)
  1 pull requests received 2 new comments:
  - #225 Pass realm when creating PerformanceResourceTiming (2 by annevk, yoavweiss)
    https://github.com/w3c/resource-timing/pull/225 

  1 pull requests merged:
  - Respec update
    https://github.com/w3c/resource-timing/pull/234 [w3c] 

* w3c/navigation-timing (+1/-0/💬1)
  1 pull requests submitted:
  - workerStart and redirects (by nicjansma)
    https://github.com/w3c/navigation-timing/pull/131 

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

* w3c/user-timing (+1/-1/💬1)
  1 pull requests submitted:
  - Query if detail is present (by npm1)
    https://github.com/w3c/user-timing/pull/75 

  1 pull requests received 1 new comments:
  - #75 Query if detail is present (1 by npm1)
    https://github.com/w3c/user-timing/pull/75 

  1 pull requests merged:
  - Query if detail is present
    https://github.com/w3c/user-timing/pull/75 


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