Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+1/-1/💬2)
  1 issues created:
  - WebCodecs Time Stamps (by sandersdan)
    https://github.com/w3c/hr-time/issues/104 

  1 issues received 2 new comments:
  - #104 WebCodecs Time Stamps (2 by npm1, sandersdan)
    https://github.com/w3c/hr-time/issues/104 

  1 issues closed:
  - WebCodecs Time Stamps https://github.com/w3c/hr-time/issues/104 

* w3c/performance-timeline (+0/-0/💬1)
  1 issues received 1 new comments:
  - #100 Ensure tests are clean (1 by sefeng211)
    https://github.com/w3c/performance-timeline/issues/100 

* w3c/resource-timing (+12/-0/💬6)
  12 issues created:
  - 4.6 Integrate the processing model with Fetch (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/252 [fetch integration] 
  - 4.5.1 "timing allow check" should be called from somewhere and get "the resource" as input (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/251 [fetch integration] 
  - 4.5 intro includes normative language but is not properly defined (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/250 [fetch integration] 
  - "Queue a task to run fire a buffer full event" needs to have a task queue (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/249 [fetch integration] 
  - 4.3 attribute getters should all be defined as part of the processing model (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/248 [fetch integration] 
  - `nextHopProtocol` needs to be defined in terms of Fetch (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/247 
  - `initiatorType` processing model needs to be defined in terms of Fetch (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/246 [fetch integration] 
  - 4.3 `startTime` and `duration` should point to the processing model (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/245 [fetch integration] 
  - Definition of `name` needs to be more precise (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/244 [fetch integration] 
  - Examples in 4.2 are not normative, but look like ones (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/243 
  - Network aborted resources SHOULD be present (not MAY) (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/242 [fetch integration] 
  - Update the editors list (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/241 

  5 issues received 6 new comments:
  - #247 `nextHopProtocol` needs to be defined in terms of Fetch (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/247 [fetch integration] 
  - #241 Update the editors list (1 by igrigorik)
    https://github.com/w3c/resource-timing/issues/241 
  - #240 Rationalize Resource-Timing opt-ins with CORS/CORP (1 by arturjanc)
    https://github.com/w3c/resource-timing/issues/240 
  - #238 transferSize might reveal HttpOnly cookies (2 by Krinkle, yoavweiss)
    https://github.com/w3c/resource-timing/issues/238 
  - #237 Are fetchStart, connectStart, redirectStart relative to navigationStart? (1 by Krinkle)
    https://github.com/w3c/resource-timing/issues/237 

* w3c/navigation-timing (+5/-0/💬0)
  5 issues created:
  - 4.2 Same origin check should have clear inputs (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/137 [fetch-integration] 
  - 4.1 Processing model should rely on Fetch/HTML (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/136 [fetch-integration] 
  - 3.3 Getters should not replicate processing model definitions (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/135 [fetch-integration] 
  - 3.2 workerTime definition (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/134 [fetch-integration] 
  - 3.1 duration definition should be done in a single place (by yoavweiss)
    https://github.com/w3c/navigation-timing/issues/133 [fetch-integration] 




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