- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 17:00:51 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1pZagF-00FD9l-Qz@uranus.w3.org>
Issues ------ * w3c/hr-time (+0/-0/💬2) 1 issues received 2 new comments: - #149 Why is EpochTimeStamp discouraged? (2 by dontcallmedom, reillyeon) https://github.com/w3c/hr-time/issues/149 * w3c/performance-timeline (+0/-0/💬14) 1 issues received 14 new comments: - #206 Proposal: clock-drift correction, potentially with opt-in (14 by Forchapeatl, GarretTomlin, noamr) https://github.com/w3c/performance-timeline/issues/206 * w3c/resource-timing (+0/-1/💬0) 1 issues closed: - User Agent may want to restrict cross-origin transferSize/encodedBodySize/decodedBodySize visibility even with TAO https://github.com/w3c/resource-timing/issues/342 * w3c/resource-hints (+0/-1/💬1) 1 issues received 1 new comments: - #48 The spec uses "navigation context" as if it was some term defined somewhere (1 by yoavweiss) https://github.com/w3c/resource-hints/issues/48 [Triaged] 1 issues closed: - The spec uses "navigation context" as if it was some term defined somewhere https://github.com/w3c/resource-hints/issues/48 [Triaged] * w3c/longtasks (+0/-0/💬3) 1 issues received 3 new comments: - #103 New proposal: long animation frames (3 by noamr, sefeng211) https://github.com/w3c/longtasks/issues/103 * w3c/server-timing (+0/-1/💬0) 1 issues closed: - Privacy and Security section should mention that a user agent may choose to not expose cross-origin PerformanceServerTiming entries even with TAO https://github.com/w3c/server-timing/issues/89 Pull requests ------------- * w3c/resource-timing (+1/-2/💬3) 1 pull requests submitted: - Tidied up document using tidy-html5 (by github-actions) https://github.com/w3c/resource-timing/pull/370 2 pull requests received 3 new comments: - #370 Tidied up document using tidy-html5 (1 by w3cbot) https://github.com/w3c/resource-timing/pull/370 - #343 Add delivery type to PerformanceResourceTiming. (2 by jeremyroman, noamr) https://github.com/w3c/resource-timing/pull/343 2 pull requests merged: - Tidied up document using tidy-html5 https://github.com/w3c/resource-timing/pull/370 - Allow user agents to enforce cross-origin restrictions https://github.com/w3c/resource-timing/pull/369 * w3c/server-timing (+0/-1/💬0) 1 pull requests merged: - Allow user agents to keep same-origin restrictions on PerformanceServ… https://github.com/w3c/server-timing/pull/90 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, 7 March 2023 17:00:53 UTC