- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 25 Apr 2023 17:00:52 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1prM28-00GRTa-0I@uranus.w3.org>
Issues ------ * w3c/hr-time (+0/-1/💬2) 1 issues received 2 new comments: - #155 Expose the "current wall time" (2 by clelland, jyasskin) https://github.com/w3c/hr-time/issues/155 1 issues closed: - Expose the "current wall time" https://github.com/w3c/hr-time/issues/155 * w3c/performance-timeline (+0/-0/💬1) 1 issues received 1 new comments: - #207 Cross-origin timeline support (1 by nicjansma) https://github.com/w3c/performance-timeline/issues/207 * w3c/resource-timing (+1/-2/💬7) 1 issues created: - Broken references in Resource Timing (by dontcallmedom-bot) https://github.com/w3c/resource-timing/issues/376 6 issues received 7 new comments: - #374 Adding resource discovery time to ResourceTiming API structure (2 by clelland, nicjansma) https://github.com/w3c/resource-timing/issues/374 - #373 Adding HTTP method to ResourceTiming API structure (1 by nicjansma) https://github.com/w3c/resource-timing/issues/373 - #371 Test infrastructure to expose whether a browser intends to expose transferSize across origins with TAO (1 by sefeng211) https://github.com/w3c/resource-timing/issues/371 - #345 Consider adding finalResponseHeaders{Start|End} times (1 by noamr) https://github.com/w3c/resource-timing/issues/345 - #262 Render blocking status of resources (1 by yoavweiss) https://github.com/w3c/resource-timing/issues/262 [enhancement] - #90 Add response status codes for resources in Resource Timing API. (1 by yoavweiss) https://github.com/w3c/resource-timing/issues/90 [enhancement] [whiteboard] [requires Fetch integration] 2 issues closed: - Render blocking status of resources https://github.com/w3c/resource-timing/issues/262 [enhancement] - Add response status codes for resources in Resource Timing API. https://github.com/w3c/resource-timing/issues/90 [enhancement] [whiteboard] [requires Fetch integration] * w3c/navigation-timing (+0/-0/💬2) 2 issues received 2 new comments: - #185 NavigationTimingType enum need updates as HTML spec changed (1 by annevk) https://github.com/w3c/navigation-timing/issues/185 - #181 Clarify how PerformanceTiming.responseStart relates to Early Hint responses (1 by noamr) https://github.com/w3c/navigation-timing/issues/181 * w3c/user-timing (+1/-0/💬0) 1 issues created: - Broken references in User Timing Level 3 (by dontcallmedom-bot) https://github.com/w3c/user-timing/issues/101 Pull requests ------------- * w3c/hr-time (+2/-2/💬1) 2 pull requests submitted: - Tidy document using tidy-html5 (by github-actions) https://github.com/w3c/hr-time/pull/162 - editorial: Add a definition for the "current wall time" without a settings object. (by jyasskin) https://github.com/w3c/hr-time/pull/161 1 pull requests received 1 new comments: - #162 Tidy document using tidy-html5 (1 by w3cbot) https://github.com/w3c/hr-time/pull/162 2 pull requests merged: - Tidy document using tidy-html5 https://github.com/w3c/hr-time/pull/162 - editorial: Add a definition for the "current wall time" without a settings object. https://github.com/w3c/hr-time/pull/161 * w3c/performance-timeline (+0/-0/💬1) 1 pull requests received 1 new comments: - #192 Add navigationId to PerformanceEntry (1 by clelland) https://github.com/w3c/performance-timeline/pull/192 * w3c/resource-timing (+0/-0/💬2) 1 pull requests received 2 new comments: - #341 Add content-type to resource-timing (2 by RByers, yoavweiss) https://github.com/w3c/resource-timing/pull/341 * w3c/user-timing (+1/-0/💬0) 1 pull requests submitted: - Editorial: nits (by npm1) https://github.com/w3c/user-timing/pull/102 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
Received on Tuesday, 25 April 2023 17:00:53 UTC