- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 14 Feb 2017 17:00:17 +0000
- To: public-web-perf@w3.org
Issues ------ * w3c/performance-timeline (+1/-0/💬10) 1 issues created: - Add "longtask" in the NOTE on valid entry types (by spanicker) https://github.com/w3c/performance-timeline/issues/69 4 issues received 10 new comments: - #66 Clarify disconnecting a PerformanceObserver that has observed entries (4 by overholt, JosephPecoraro, hiikezoe, toddreifsteck) https://github.com/w3c/performance-timeline/issues/66 - #68 performance.timing shouldn't be deprecated (4 by rniwa, igrigorik, toddreifsteck) https://github.com/w3c/performance-timeline/issues/68 - #65 Clarify how PerformanceObserver invokes the callback - arguments and `this` value (1 by toddreifsteck) https://github.com/w3c/performance-timeline/issues/65 - #67 Clarify sort order for entries with equivalent startTime (1 by toddreifsteck) https://github.com/w3c/performance-timeline/issues/67 * w3c/resource-timing (+4/-0/💬6) 4 issues created: - Custom ABNF Syntax specification (by JosephPecoraro) https://github.com/w3c/resource-timing/issues/99 - Graphic should indicate fetchStart is a required field, not a parenthesized zeroed field (by JosephPecoraro) https://github.com/w3c/resource-timing/issues/98 - Clarify behavior of setResourceTimingBufferSize (by JosephPecoraro) https://github.com/w3c/resource-timing/issues/96 - Clarify resourcetimingbufferfull conditions (by JosephPecoraro) https://github.com/w3c/resource-timing/issues/95 4 issues received 6 new comments: - #93 Determine whether to wait until after responseEnd to queue entry for ResourceTiming (2 by JosephPecoraro, spanicker) https://github.com/w3c/resource-timing/issues/93 - #89 Increase limit of 150 for PerformanceEntrys? (2 by igrigorik, nicjansma) https://github.com/w3c/resource-timing/issues/89 - #82 Clarify when entry is added to performance entry buffer (1 by JosephPecoraro) https://github.com/w3c/resource-timing/issues/82 - #55 Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? (1 by JosephPecoraro) https://github.com/w3c/resource-timing/issues/55 * w3c/preload (+2/-0/💬15) 2 issues created: - `type` and `media` processing missing from "obtain the preload resource" (by yoavweiss) https://github.com/w3c/preload/issues/86 - Specifying or using preload twice (by yutakahirano) https://github.com/w3c/preload/issues/85 2 issues received 15 new comments: - #85 Specifying or using preload twice (14 by igrigorik, annevk, yutakahirano, yoavweiss) https://github.com/w3c/preload/issues/85 - #84 Difference between Link: rel=preload header and the link HTML element (1 by pelchats) https://github.com/w3c/preload/issues/84 Pull requests ------------- * w3c/resource-timing (+1/-0/💬1) 1 pull requests submitted: - Merge V2 into gh-pages (by yoavweiss) https://github.com/w3c/resource-timing/pull/97 1 pull requests received 1 new comments: - #97 Merge V2 into gh-pages (1 by igrigorik) https://github.com/w3c/resource-timing/pull/97 * w3c/beacon (+0/-0/💬1) 1 pull requests received 1 new comments: - #39 (WIP) Enforce payload limits via Fetch API (1 by igrigorik) https://github.com/w3c/beacon/pull/39 * w3c/preload (+1/-0/💬0) 1 pull requests submitted: - Fix up `type`,`media` and `href` processing (by yoavweiss) https://github.com/w3c/preload/pull/87 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
Received on Tuesday, 14 February 2017 17:00:24 UTC