- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2017 17:00:13 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1e1xt7-0007DV-48@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+6/-3/💬2) 6 issues created: - Steps 3 and 4 of observe() isn't clear about what list is being considered (by bzbarsky) https://github.com/w3c/performance-timeline/issues/94 - observe() step 3 is confused about what objects it's manipulating (by bzbarsky) https://github.com/w3c/performance-timeline/issues/93 - Need to define what it means for an element of entryTypes to be "unsupported" (by bzbarsky) https://github.com/w3c/performance-timeline/issues/92 - Does PerformanceObserverInit's entryTypes contain types or names? (by bzbarsky) https://github.com/w3c/performance-timeline/issues/91 - Step 1 of observe() gets an entryTypes sequence from ... where? (by bzbarsky) https://github.com/w3c/performance-timeline/issues/90 - Step 1 of "observe" is not clear (by bzbarsky) https://github.com/w3c/performance-timeline/issues/89 2 issues received 2 new comments: - #92 Need to define what it means for an element of entryTypes to be "unsupported" (1 by igrigorik) https://github.com/w3c/performance-timeline/issues/92 - #89 Step 1 of "observe" is not clear (1 by igrigorik) https://github.com/w3c/performance-timeline/issues/89 3 issues closed: - Need to define what it means for an element of entryTypes to be "unsupported" https://github.com/w3c/performance-timeline/issues/92 - Step 1 of "observe" is not clear https://github.com/w3c/performance-timeline/issues/89 - Should PerformanceObserver throw when entryTypes is empty? https://github.com/w3c/performance-timeline/issues/87 * w3c/resource-timing (+2/-0/💬10) 2 issues created: - spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (by wanderview) https://github.com/w3c/resource-timing/issues/119 - should redirected navigations have a workerStart value if a previous redirect URL was intercepted (by wanderview) https://github.com/w3c/resource-timing/issues/118 1 issues received 10 new comments: - #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (10 by mattto, wanderview) https://github.com/w3c/resource-timing/issues/119 * w3c/preload (+1/-1/💬8) 1 issues created: - Parsable MIME type is going away (by annevk) https://github.com/w3c/preload/issues/113 2 issues received 8 new comments: - #112 Performance impact? (4 by igrigorik, edent, yoavweiss, addyosmani) https://github.com/w3c/preload/issues/112 - #113 Parsable MIME type is going away (4 by annevk, yoavweiss) https://github.com/w3c/preload/issues/113 1 issues closed: - Privacy and security questionnaire self-assesment https://github.com/w3c/preload/issues/111 * w3c/requestidlecallback (+1/-0/💬1) 1 issues created: - (Editorial) Example 1 does not render properly (by iherman) https://github.com/w3c/requestidlecallback/issues/67 1 issues received 1 new comments: - #67 (Editorial) Example 1 does not render properly (1 by igrigorik) https://github.com/w3c/requestidlecallback/issues/67 * w3c/server-timing (+1/-0/💬2) 1 issues created: - readdress TAO (by cvazac) https://github.com/w3c/server-timing/issues/35 1 issues received 2 new comments: - #35 readdress TAO (2 by igrigorik, yoavweiss) https://github.com/w3c/server-timing/issues/35 Pull requests ------------- * w3c/hr-time (+1/-1/💬5) 1 pull requests submitted: - Example currently broken in latest/published versions (by ericduran) https://github.com/w3c/hr-time/pull/52 1 pull requests received 5 new comments: - #52 Example currently broken in latest/published versions (5 by igrigorik, plehegar, ericduran) https://github.com/w3c/hr-time/pull/52 1 pull requests merged: - Example currently broken in latest/published versions https://github.com/w3c/hr-time/pull/52 * w3c/performance-timeline (+2/-1/💬4) 2 pull requests submitted: - Improve observe() logic and references (by igrigorik) https://github.com/w3c/performance-timeline/pull/96 - [WIP] Explain and improve PerformanceObserver ergonomics (by igrigorik) https://github.com/w3c/performance-timeline/pull/95 3 pull requests received 4 new comments: - #84 Fix auto-publish (2 by igrigorik, siusin) https://github.com/w3c/performance-timeline/pull/84 - #88 observing an empty sequence of entryTypes is a no-op (1 by igrigorik) https://github.com/w3c/performance-timeline/pull/88 - #95 [WIP] Explain and improve PerformanceObserver ergonomics (1 by igrigorik) https://github.com/w3c/performance-timeline/pull/95 1 pull requests merged: - observing an empty sequence of entryTypes is a no-op https://github.com/w3c/performance-timeline/pull/88 * w3c/server-timing (+1/-0/💬0) 1 pull requests submitted: - Exclude PerformanceServerTiming objects for resources that fail the "timing allow check" algorithm (by cvazac) https://github.com/w3c/server-timing/pull/36 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, 10 October 2017 17:00:01 UTC