- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 16 Oct 2018 17:00:25 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1gCShl-00026G-Ej@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+0/-0/💬2) 2 issues received 2 new comments: - #81 Define buffering behaviors & hooks for queued (PerformanceObserver) entries (1 by rniwa) https://github.com/w3c/performance-timeline/issues/81 [enhancement] - #105 PerformanceEntries are affected by backgrounded status (1 by npm1) https://github.com/w3c/performance-timeline/issues/105 * w3c/resource-timing (+2/-1/💬14) 2 issues created: - Clarify cross-origin resources (by alanwaketan) https://github.com/w3c/resource-timing/issues/173 - Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming (by miketaylr) https://github.com/w3c/resource-timing/issues/167 5 issues received 14 new comments: - #152 `origin-or-null` definition and TAO processing (10 by marcoscaceres, annevk, yoavweiss) https://github.com/w3c/resource-timing/issues/152 [Clarification] [needs tests] - #160 DNS lookups can occur even when reusing a connection (1 by yoavweiss) https://github.com/w3c/resource-timing/issues/160 - #164 elaborate on `stalled` or `blocked` stage in specs (1 by jasonslyvia) https://github.com/w3c/resource-timing/issues/164 - #167 Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming (1 by yoavweiss) https://github.com/w3c/resource-timing/issues/167 - #173 Clarify cross-origin resources (1 by annevk) https://github.com/w3c/resource-timing/issues/173 1 issues closed: - Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming https://github.com/w3c/resource-timing/issues/167 * w3c/user-timing (+0/-0/💬2) 2 issues received 2 new comments: - #14 Handling repeat metrics and measures + custom startTime? (1 by jakub-g) https://github.com/w3c/user-timing/issues/14 [whiteboard] - #23 mark() and measure() return PerformanceEntries (1 by jakub-g) https://github.com/w3c/user-timing/issues/23 [enhancement] * w3c/preload (+1/-0/💬6) 1 issues created: - Preloading images corresponding to picture element (by domfarolino) https://github.com/w3c/preload/issues/131 3 issues received 6 new comments: - #121 can the browser place limits on the preload cache? (2 by yoavweiss, wanderview) https://github.com/w3c/preload/issues/121 - #114 Interaction of 103 and CSP (2 by annevk, yoavweiss) https://github.com/w3c/preload/issues/114 [non-blocking] - #113 Parsable MIME type is going away (2 by annevk, yoavweiss) https://github.com/w3c/preload/issues/113 [editorial] * w3c/resource-hints (+0/-1/💬2) 1 issues received 2 new comments: - #82 Prefetch and double-key caching (2 by yoavweiss, youennf) https://github.com/w3c/resource-hints/issues/82 1 issues closed: - Dead references to `pr` attribute https://github.com/w3c/resource-hints/issues/81 * w3c/requestidlecallback (+0/-0/💬2) 1 issues received 2 new comments: - #70 Missing definition for "idle time" (2 by yoavweiss, domenic) https://github.com/w3c/requestidlecallback/issues/70 [bug] [enhancement] * w3c/device-memory (+0/-1/💬1) 1 issues received 1 new comments: - #10 JavaScript API support (1 by yoavweiss) https://github.com/w3c/device-memory/issues/10 1 issues closed: - JavaScript API support https://github.com/w3c/device-memory/issues/10 Pull requests ------------- * w3c/performance-timeline (+1/-1/💬2) 1 pull requests submitted: - Fix links after dependency removal (by yoavweiss) https://github.com/w3c/performance-timeline/pull/109 1 pull requests received 2 new comments: - #107 Remove dependencies section (2 by npm1, yoavweiss) https://github.com/w3c/performance-timeline/pull/107 1 pull requests merged: - Fix links after dependency removal https://github.com/w3c/performance-timeline/pull/109 * w3c/resource-timing (+5/-2/💬2) 5 pull requests submitted: - Use HTML's origin serialization, add note regarding TAO and redirects (by yoavweiss) https://github.com/w3c/resource-timing/pull/172 - Removed ! from performance entry buffer links (by yoavweiss) https://github.com/w3c/resource-timing/pull/171 - editorials: update links (by marcoscaceres) https://github.com/w3c/resource-timing/pull/170 - Add a note about "stalled" or "blocked" time (by jasonslyvia) https://github.com/w3c/resource-timing/pull/169 - Fire `resourcetimingbufferfull` asynchronously - alternative approach (by yoavweiss) https://github.com/w3c/resource-timing/pull/168 1 pull requests received 2 new comments: - #170 editorial: update links (2 by marcoscaceres) https://github.com/w3c/resource-timing/pull/170 2 pull requests merged: - Removed ! from performance entry buffer links https://github.com/w3c/resource-timing/pull/171 - editorial: update links https://github.com/w3c/resource-timing/pull/170 * w3c/page-visibility (+0/-0/💬1) 1 pull requests received 1 new comments: - #38 clarify UA may be hidden when fully obscured (1 by yoavweiss) https://github.com/w3c/page-visibility/pull/38 [a11y] * w3c/resource-hints (+0/-1/💬0) 1 pull requests merged: - Remove mentions of 'pr' attribute. https://github.com/w3c/resource-hints/pull/83 * w3c/paint-timing (+1/-1/💬0) 1 pull requests submitted: - Update broken link in README (by everdimension) https://github.com/w3c/paint-timing/pull/34 1 pull requests merged: - Update broken link in README https://github.com/w3c/paint-timing/pull/34 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, 16 October 2018 17:00:32 UTC