Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+0/-1/💬1)
  1 issues received 1 new comments:
  - #136 Prerendered pages and `timeOrigin` (1 by yoavweiss)
    https://github.com/w3c/hr-time/issues/136 

  1 issues closed:
  - Prerendered pages and `timeOrigin` https://github.com/w3c/hr-time/issues/136 

* w3c/resource-timing (+1/-1/💬3)
  1 issues created:
  - Drop the "L2" part from the published version (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/326 

  2 issues received 3 new comments:
  - #303 Reflect preload information (in ResourceTiming?) (1 by noamr)
    https://github.com/w3c/resource-timing/issues/303 [enhancement] 
  - #142 `InitiatorType` should not single out XHR (2 by annevk, noamr)
    https://github.com/w3c/resource-timing/issues/142 [Clarification] 

  1 issues closed:
  - elaborate on `stalled` or `blocked` stage in specs https://github.com/w3c/resource-timing/issues/164 [Clarification] 

* w3c/navigation-timing (+0/-0/💬2)
  1 issues received 2 new comments:
  - #160 Using navigationStart as a baseline may expose cross-origin timing information (2 by annevk, noamr)
    https://github.com/w3c/navigation-timing/issues/160 

* w3c/beacon (+1/-0/💬0)
  1 issues created:
  - Setup auto publishing (by yoavweiss)
    https://github.com/w3c/beacon/issues/76 

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

* w3c/preload (+0/-1/💬1)
  1 issues received 1 new comments:
  - #113 Parsable MIME type is going away (1 by noamr)
    https://github.com/w3c/preload/issues/113 [HTML integration] 

  1 issues closed:
  - Interaction of 103 and CSP https://github.com/w3c/preload/issues/114 [HTML integration] [non-blocking] 

* w3c/resource-hints (+0/-0/💬1)
  1 issues received 1 new comments:
  - #74 Sending a `Purpose: prefetch` header for prefetched resources (1 by tigt)
    https://github.com/w3c/resource-hints/issues/74 [Prefetch] [Triaged] 

* w3c/requestidlecallback (+1/-1/💬0)
  1 issues created:
  - Setup auto publishing (by yoavweiss)
    https://github.com/w3c/requestidlecallback/issues/100 

  1 issues closed:
  - Can we rename this spec? https://github.com/w3c/requestidlecallback/issues/91 

* w3c/longtasks (+0/-1/💬5)
  1 issues received 5 new comments:
  - #98 Task duration should be coarsened for each context (5 by domenic, noamr, yoavweiss)
    https://github.com/w3c/longtasks/issues/98 

  1 issues closed:
  - Task duration should be coarsened for each context https://github.com/w3c/longtasks/issues/98 



Pull requests
-------------
* w3c/resource-timing (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #323 Illustrate in diagram that timestamps are not necessarily consecutive (1 by yoavweiss)
    https://github.com/w3c/resource-timing/pull/323 

  1 pull requests merged:
  - Illustrate in diagram that timestamps are not necessarily consecutive
    https://github.com/w3c/resource-timing/pull/323 

* w3c/requestidlecallback (+0/-1/💬0)
  1 pull requests merged:
  - Editorial: rename spec to requestIdleCallback()
    https://github.com/w3c/requestidlecallback/pull/92 

* w3c/longtasks (+1/-1/💬0)
  1 pull requests submitted:
  - Coarsen timestamps when reporting (by noamr)
    https://github.com/w3c/longtasks/pull/99 

  1 pull requests merged:
  - Coarsen timestamps when reporting
    https://github.com/w3c/longtasks/pull/99 


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