Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-0/💬2)
  2 issues received 2 new comments:
  - #88 High resolution time is not defined (1 by mmocny)
    https://github.com/w3c/hr-time/issues/88 [editorial] [enhancement] 
  - #87 Provide hook for getting a high resolution time between time origin and a "time" (1 by igneel64)
    https://github.com/w3c/hr-time/issues/87 [editorial] [enhancement] 

* w3c/performance-timeline (+0/-1/💬1)
  1 issues received 1 new comments:
  - #81 Define buffering behaviors & hooks for queued (PerformanceObserver) entries (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/81 [enhancement] 

  1 issues closed:
  - Define buffering behaviors & hooks for queued (PerformanceObserver) entries https://github.com/w3c/performance-timeline/issues/81 [enhancement] 

* w3c/resource-timing (+1/-1/💬2)
  1 issues created:
  - ResourceTiming Test Triage 9/2020 (by nicjansma)
    https://github.com/w3c/resource-timing/issues/233 

  1 issues received 2 new comments:
  - #220 Provide a TAO-bypass for Navigation timing (2 by caribouW3, yoavweiss)
    https://github.com/w3c/resource-timing/issues/220 [editorial] 

  1 issues closed:
  - The step to queue a task to run fire a buffer full event should specify its source https://github.com/w3c/resource-timing/issues/215 

* w3c/navigation-timing (+0/-2/💬2)
  1 issues received 2 new comments:
  - #115 Definition of "back_forward" navigation type does not make sense (2 by npm1, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/115 

  2 issues closed:
  - Definition of "back_forward" navigation type does not make sense https://github.com/w3c/navigation-timing/issues/115 
  - Can hitting enter on address bar to same URL be considered a navigation of type 'reload'? https://github.com/w3c/navigation-timing/issues/116 [enhancement] 

* w3c/page-visibility (+0/-1/💬1)
  1 issues received 1 new comments:
  - #63 Treating .hidden as "historical" seems unhelpful (1 by marcoscaceres)
    https://github.com/w3c/page-visibility/issues/63 

  1 issues closed:
  - Treating .hidden as "historical" seems unhelpful https://github.com/w3c/page-visibility/issues/63 

* w3c/preload (+0/-0/💬1)
  1 issues received 1 new comments:
  - #154 Link to or merge with HTML definition of "preload" (1 by plehegar)
    https://github.com/w3c/preload/issues/154 



Pull requests
-------------
* w3c/hr-time (+3/-0/💬6)
  3 pull requests submitted:
  - Define 'relative high resolution time' (by igneel64)
    https://github.com/w3c/hr-time/pull/95 
  - Add a <dfn> for "high resolution time" (by mmocny)
    https://github.com/w3c/hr-time/pull/94 
  - Limit the timer resolution in non-isolated contexts (by yoavweiss)
    https://github.com/w3c/hr-time/pull/93 

  2 pull requests received 6 new comments:
  - #94 Add a <dfn> for "high resolution time" (3 by annevk, mmocny)
    https://github.com/w3c/hr-time/pull/94 
  - #93 Limit the timer resolution in non-isolated contexts (3 by npm1, yoavweiss)
    https://github.com/w3c/hr-time/pull/93 

* w3c/performance-timeline (+1/-1/💬0)
  1 pull requests submitted:
  - Add dfn to performance timeline task source (by npm1)
    https://github.com/w3c/performance-timeline/pull/175 

  1 pull requests merged:
  - Add dfn to performance timeline task source
    https://github.com/w3c/performance-timeline/pull/175 

* w3c/resource-timing (+2/-1/💬0)
  2 pull requests submitted:
  - Respec update (by plehegar)
    https://github.com/w3c/resource-timing/pull/234 
  - Add task source to queue a task (by npm1)
    https://github.com/w3c/resource-timing/pull/232 

  1 pull requests merged:
  - Add task source to queue a task
    https://github.com/w3c/resource-timing/pull/232 

* w3c/navigation-timing (+2/-2/💬0)
  2 pull requests submitted:
  - Use PP2017 (by plehegar)
    https://github.com/w3c/navigation-timing/pull/130 
  - Point navigation type values to HTML spec's new history handling (by gi11es)
    https://github.com/w3c/navigation-timing/pull/129 

  2 pull requests merged:
  - Use PP2017
    https://github.com/w3c/navigation-timing/pull/130 [w3c] 
  - Point navigation type values to HTML spec's new history handling
    https://github.com/w3c/navigation-timing/pull/129 

* w3c/page-visibility (+0/-1/💬0)
  1 pull requests merged:
  - Editorial: remove note about hidden being 'historical'
    https://github.com/w3c/page-visibility/pull/64 

* w3c/preload (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #149 add an attribute to hint the server which headers to copy in push requests (1 by dunglas)
    https://github.com/w3c/preload/pull/149 


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