- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 20 Apr 2021 17:00:47 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1lYtjz-0000qh-5i@uranus.w3.org>
Issues ------ * w3c/resource-timing (+0/-8/💬11) 9 issues received 11 new comments: - #264 Add tests for TAO-fail behavior changes since FETCH integration (2 by noamr, npm1) https://github.com/w3c/resource-timing/issues/264 [fetch-integration] - #256 Remove reference to "relevant application cache" and replace it with Fetch concepts (1 by bdekoz) https://github.com/w3c/resource-timing/issues/256 [fetch-integration] - #247 `nextHopProtocol` needs to be defined in terms of Fetch (1 by noamr) https://github.com/w3c/resource-timing/issues/247 [fetch-integration] - #246 `initiatorType` processing model needs to be defined in terms of Fetch (1 by noamr) https://github.com/w3c/resource-timing/issues/246 [fetch-integration] - #245 4.3 `startTime` and `duration` should point to the processing model (1 by noamr) https://github.com/w3c/resource-timing/issues/245 [fetch-integration] - #244 Definition of `name` needs to be more precise (1 by noamr) https://github.com/w3c/resource-timing/issues/244 [fetch-integration] - #226 Pass realm when creating PerformanceResourceTiming (1 by noamr) https://github.com/w3c/resource-timing/issues/226 [Clarification] [fetch-integration] - #90 Add response status codes for resources in Resource Timing API. (1 by mehulkar) https://github.com/w3c/resource-timing/issues/90 [enhancement] [requires Fetch integration] [whiteboard] - #39 Define Resource Timing in terms of Fetch (2 by noamr, yoavweiss) https://github.com/w3c/resource-timing/issues/39 [Clarification] [fetch-integration] 8 issues closed: - Add tests for TAO-fail behavior changes since FETCH integration https://github.com/w3c/resource-timing/issues/264 [fetch-integration] - transferSize might reveal HttpOnly cookies https://github.com/w3c/resource-timing/issues/238 [requires Fetch integration] - Pass realm when creating PerformanceResourceTiming https://github.com/w3c/resource-timing/issues/226 [Clarification] [fetch-integration] - `nextHopProtocol` needs to be defined in terms of Fetch https://github.com/w3c/resource-timing/issues/247 [fetch-integration] - `initiatorType` processing model needs to be defined in terms of Fetch https://github.com/w3c/resource-timing/issues/246 [fetch-integration] - 4.3 `startTime` and `duration` should point to the processing model https://github.com/w3c/resource-timing/issues/245 [fetch-integration] - Define Resource Timing in terms of Fetch https://github.com/w3c/resource-timing/issues/39 [Clarification] [fetch-integration] - Definition of `name` needs to be more precise https://github.com/w3c/resource-timing/issues/244 [fetch-integration] * w3c/navigation-timing (+2/-3/💬11) 2 issues created: - list of possible initiator types from the resource timing API? (by ThierryMajutec) https://github.com/w3c/navigation-timing/issues/145 - Clarify security context for PerformanceNavigationTiming (by fred-wang) https://github.com/w3c/navigation-timing/issues/144 6 issues received 11 new comments: - #144 Clarify security context for PerformanceNavigationTiming (4 by fred-wang, noamr, npm1) https://github.com/w3c/navigation-timing/issues/144 - #137 4.2 Same origin check should have clear inputs (1 by noamr) https://github.com/w3c/navigation-timing/issues/137 [fetch-integration] - #135 3.3 Getters should not replicate processing model definitions (1 by noamr) https://github.com/w3c/navigation-timing/issues/135 [fetch-integration] - #134 3.2 workerTime definition (2 by noamr, yoavweiss) https://github.com/w3c/navigation-timing/issues/134 [fetch-integration] - #133 3.1 duration definition should be done in a single place (2 by noamr) https://github.com/w3c/navigation-timing/issues/133 [fetch-integration] - #125 PerformanceNavigationTiming needs a realm (1 by noamr) https://github.com/w3c/navigation-timing/issues/125 [clarification] [fetch-integration] 3 issues closed: - 3.3 Getters should not replicate processing model definitions https://github.com/w3c/navigation-timing/issues/135 [fetch-integration] - 4.2 Same origin check should have clear inputs https://github.com/w3c/navigation-timing/issues/137 [fetch-integration] - PerformanceNavigationTiming needs a realm https://github.com/w3c/navigation-timing/issues/125 [clarification] [fetch-integration] * w3c/server-timing (+1/-0/💬0) 1 issues created: - Clarify security context for PerformanceNavigationTiming (by fred-wang) https://github.com/w3c/server-timing/issues/79 Pull requests ------------- * w3c/resource-timing (+4/-4/💬1) 4 pull requests submitted: - Remove stray <<< HEAD (by noamr) https://github.com/w3c/resource-timing/pull/270 - Remove stray <<<< (by noamr) https://github.com/w3c/resource-timing/pull/269 - Fix exports (by yoavweiss) https://github.com/w3c/resource-timing/pull/268 - Initial attempt at autopublishing (by yoavweiss) https://github.com/w3c/resource-timing/pull/267 1 pull requests received 1 new comments: - #266 Expose transferSize, encodedBodySize, decodedBodySize (1 by noamr) https://github.com/w3c/resource-timing/pull/266 4 pull requests merged: - Remove stray <<< HEAD https://github.com/w3c/resource-timing/pull/270 - Expose transferSize, encodedBodySize, decodedBodySize https://github.com/w3c/resource-timing/pull/266 - Fix exports https://github.com/w3c/resource-timing/pull/268 - Initial attempt at autopublishing https://github.com/w3c/resource-timing/pull/267 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, 20 April 2021 17:00:49 UTC