- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 28 Jan 2020 17:00:53 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1iwUEP-0006cu-6S@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+1/-1/💬2) 1 issues created: - Are we always supposed to queue a notification task when there are buffered entries to see? (by pshaughn) https://github.com/w3c/performance-timeline/issues/158 2 issues received 2 new comments: - #158 Are we always supposed to queue a notification task when there are buffered entries to see? (1 by npm1) https://github.com/w3c/performance-timeline/issues/158 - #100 Ensure tests are clean (1 by npm1) https://github.com/w3c/performance-timeline/issues/100 1 issues closed: - Are we always supposed to queue a notification task when there are buffered entries to see? https://github.com/w3c/performance-timeline/issues/158 * w3c/resource-timing (+1/-1/💬4) 1 issues created: - Provide a TAO-bypass for Navigation timing (by yoavweiss) https://github.com/w3c/resource-timing/issues/220 3 issues received 4 new comments: - #215 The step to queue a task to run fire a buffer full event should specify its source (1 by npm1) https://github.com/w3c/resource-timing/issues/215 - #210 Cross-origin IFRAME opting-in to sharing ResourceTiming data (2 by npm1, yoavweiss) https://github.com/w3c/resource-timing/issues/210 - #190 Expose JavaScript code caching information in PerformanceResourceTiming (1 by mathiasbynens) https://github.com/w3c/resource-timing/issues/190 [enhancement] [whiteboard] 1 issues closed: - Handling of 0-RTT interactions https://github.com/w3c/resource-timing/issues/199 * w3c/navigation-timing (+0/-1/💬7) 2 issues received 7 new comments: - #118 Add a new entry type for navigations from the BFCache (5 by npm1, philipwalton) https://github.com/w3c/navigation-timing/issues/118 - #115 Definition of "back_forward" navigation type does not make sense (2 by npm1, yoavweiss) https://github.com/w3c/navigation-timing/issues/115 1 issues closed: - Add a new entry type for navigations from the BFCache https://github.com/w3c/navigation-timing/issues/118 * w3c/page-visibility (+2/-0/💬3) 2 issues created: - The spec's definition of hidden is unclear and should be updated to better account for mobile use cases (by philipwalton) https://github.com/w3c/page-visibility/issues/59 - Switching tabs in Safari for iOS still displays the elements that should be invisible (by envilgt) https://github.com/w3c/page-visibility/issues/58 1 issues received 3 new comments: - #58 Switching tabs in Safari for iOS still displays the elements that should be hidden (3 by philipwalton, rniwa, yoavweiss) https://github.com/w3c/page-visibility/issues/58 * w3c/preload (+0/-1/💬1) 1 issues received 1 new comments: - #139 Specifying Range in Link preload header for HTTP/2 Push (1 by roger-on-github) https://github.com/w3c/preload/issues/139 [discuss] 1 issues closed: - Specifying Range in Link preload header for HTTP/2 Push https://github.com/w3c/preload/issues/139 [discuss] * w3c/resource-hints (+1/-1/💬2) 1 issues created: - W3 Validator reports error for <link> with `as` attribute (by iamkumaran) https://github.com/w3c/resource-hints/issues/93 1 issues received 2 new comments: - #93 Alignment with HTML spec on "as" attribute definition (2 by dontcallmedom, yoavweiss) https://github.com/w3c/resource-hints/issues/93 1 issues closed: - Alignment with HTML spec on "as" attribute definition https://github.com/w3c/resource-hints/issues/93 * w3c/paint-timing (+0/-1/💬1) 1 issues received 1 new comments: - #46 The code example incorrectly mentions observing "long tasks" (1 by npm1) https://github.com/w3c/paint-timing/issues/46 1 issues closed: - The code example incorrectly mentions observing "long tasks" https://github.com/w3c/paint-timing/issues/46 * w3c/server-timing (+1/-1/💬5) 1 issues created: - Exposing data on production (by SilentImp) https://github.com/w3c/server-timing/issues/71 2 issues received 5 new comments: - #71 Exposing data on production (1 by yoavweiss) https://github.com/w3c/server-timing/issues/71 - #65 Using Server-timing to carry TraceID (4 by SilentImp, plehegar, yoavweiss) https://github.com/w3c/server-timing/issues/65 [question] 1 issues closed: - Exposing data on production https://github.com/w3c/server-timing/issues/71 Pull requests ------------- * w3c/performance-timeline (+1/-1/💬0) 1 pull requests submitted: - Fix observe() with buffered flag (by npm1) https://github.com/w3c/performance-timeline/pull/159 1 pull requests merged: - Fix observe() with buffered flag https://github.com/w3c/performance-timeline/pull/159 * w3c/resource-timing (+0/-1/💬0) 1 pull requests merged: - Zero RTT clarifications from davidben https://github.com/w3c/resource-timing/pull/219 * w3c/device-memory (+1/-1/💬1) 1 pull requests submitted: - Convert NavigatorDeviceClass to an interface mixin (by foolip) https://github.com/w3c/device-memory/pull/25 1 pull requests received 1 new comments: - #25 Convert NavigatorDeviceClass to an interface mixin (1 by foolip) https://github.com/w3c/device-memory/pull/25 1 pull requests merged: - Convert NavigatorDeviceClass to an interface mixin https://github.com/w3c/device-memory/pull/25 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
Received on Tuesday, 28 January 2020 17:00:55 UTC