Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/resource-timing (+0/-0/💬2)
  2 issues received 2 new comments:
  - #326 Drop the "L2" part from the published version (1 by caribouW3)
    https://github.com/w3c/resource-timing/issues/326 
  - #203 Include Content Type (1 by alonkochba)
    https://github.com/w3c/resource-timing/issues/203 [enhancement] 

* w3c/navigation-timing (+1/-0/💬6)
  1 issues created:
  - Report that Critical-CH was used to restart a navigation (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/177 

  3 issues received 6 new comments:
  - #163 How should prefetch be exposed? (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/163 
  - #154 Lack of Feature Parity with Performace.measure() in Level 2 (2 by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/154 
  - #149 The "Obsolete" label is rendered in a seemingly random place (3 by noamr, yoavweiss)
    https://github.com/w3c/navigation-timing/issues/149 

* w3c/user-timing (+1/-1/💬7)
  1 issues created:
  - It is unclear what "If startOrMeasureOptions is a non-empty PerformanceMeasureOptions object" means (by smaug----)
    https://github.com/w3c/user-timing/issues/89 

  2 issues received 7 new comments:
  - #89 It is unclear what "If startOrMeasureOptions is a non-empty PerformanceMeasureOptions object" means (5 by npm1, smaug----, yoavweiss)
    https://github.com/w3c/user-timing/issues/89 
  - #86 Contextual and GC friendly user timing (2 by legendecas, yoavweiss)
    https://github.com/w3c/user-timing/issues/86 [enhancement] [triaged] 

  1 issues closed:
  - It is unclear what "If startOrMeasureOptions is a non-empty PerformanceMeasureOptions object" means https://github.com/w3c/user-timing/issues/89 

* w3c/beacon (+0/-0/💬3)
  1 issues received 3 new comments:
  - #76 Setup auto publishing (3 by caribouW3, yoavweiss)
    https://github.com/w3c/beacon/issues/76 

* w3c/page-visibility (+0/-1/💬3)
  1 issues received 3 new comments:
  - #70 can we drop level? (3 by caribouW3, yoavweiss)
    https://github.com/w3c/page-visibility/issues/70 

  1 issues closed:
  - can we drop level? https://github.com/w3c/page-visibility/issues/70 

* w3c/preload (+0/-1/💬2)
  1 issues received 2 new comments:
  - #130 Putting an upper limit on preload/prefetch chains (2 by noamr, yoavweiss)
    https://github.com/w3c/preload/issues/130 [HTML integration] [prose] 

  1 issues closed:
  - Putting an upper limit on preload/prefetch chains https://github.com/w3c/preload/issues/130 [HTML integration] [prose] 

* w3c/resource-hints (+0/-0/💬5)
  1 issues received 5 new comments:
  - #66 Processing model for `as`? (5 by hiroshige-g, noamr, yoavweiss)
    https://github.com/w3c/resource-hints/issues/66 [Prefetch] [definition] [Triaged] 

* w3c/server-timing (+0/-3/💬1)
  1 issues received 1 new comments:
  - #69 Creation time of PerformanceServerTiming objects unclear (1 by annevk)
    https://github.com/w3c/server-timing/issues/69 [definition] 

  3 issues closed:
  - Creation time of PerformanceServerTiming objects unclear https://github.com/w3c/server-timing/issues/69 [definition] 
  - Evaluate current parsing error strategy https://github.com/w3c/server-timing/issues/42 [definition] 
  - Fetch integration is missing https://github.com/w3c/server-timing/issues/55 [definition] 



Pull requests
-------------
* w3c/user-timing (+1/-0/💬0)
  1 pull requests submitted:
  - Remove incorrect non-empty check (by npm1)
    https://github.com/w3c/user-timing/pull/90 

* w3c/server-timing (+0/-1/💬0)
  1 pull requests merged:
  - Add explicit parsing rules for FETCH integration
    https://github.com/w3c/server-timing/pull/87 


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