- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 06 Dec 2016 17:00:07 +0000
- To: public-web-perf@w3.org
Issues ------ * w3c/resource-timing (+1/-2/💬4) 1 issues created: - Clarify when entry is added to performance entry buffer (by igrigorik) https://github.com/w3c/resource-timing/issues/82 2 issues closed: - Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? https://github.com/w3c/resource-timing/issues/55 - Initiator is not well defined https://github.com/w3c/resource-timing/issues/69 3 issues received 4 new comments: - #63 Clarify definition of responseStart (2 by igrigorik, toddreifsteck) https://github.com/w3c/resource-timing/issues/63 - #69 Initiator is not well defined (1 by igrigorik) https://github.com/w3c/resource-timing/issues/69 - #55 Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? (1 by igrigorik) https://github.com/w3c/resource-timing/issues/55 * w3c/navigation-timing (+2/-2/💬5) 2 issues created: - Links in status section are broken (by bripkens) https://github.com/w3c/navigation-timing/issues/54 - Clarify TAO check for unloadEventStart|End (by spanicker) https://github.com/w3c/navigation-timing/issues/53 2 issues closed: - Processing Model is confusing in respect of startTime and beforeunload https://github.com/w3c/navigation-timing/issues/48 - Processing Model chart is missing domLoading marker https://github.com/w3c/navigation-timing/issues/44 2 issues received 5 new comments: - #50 data bias issues due to deferring reporting of all nav timing metrics to the load event (4 by igrigorik, bmaurer) https://github.com/w3c/navigation-timing/issues/50 - #48 Processing Model is confusing in respect of startTime and beforeunload (1 by igrigorik) https://github.com/w3c/navigation-timing/issues/48 * w3c/preload (+0/-1/💬3) 1 issues closed: - Define preload cache and request matching algorithm https://github.com/w3c/preload/issues/30 1 issues received 3 new comments: - #80 Require "as" attribute (3 by igrigorik, AshleyScirra) https://github.com/w3c/preload/issues/80 * w3c/requestidlecallback (+0/-0/💬2) 2 issues received 2 new comments: - #44 diagram with frame commit and vsync is inaccurate for some browsers (1 by igrigorik) https://github.com/w3c/requestidlecallback/issues/44 - #47 It is unclear what IdleDeadline.timeRemaining() should return if JS keeps the IdleDealing object alive even after the callback call. (1 by bzbarsky) https://github.com/w3c/requestidlecallback/issues/47 Pull requests ------------- * w3c/resource-timing (+4/-6/💬10) 4 pull requests submitted: - Typo fix (by xfq) https://github.com/w3c/resource-timing/pull/86 - s/MUST/MAY semantics for failed fetches in L2 (by igrigorik) https://github.com/w3c/resource-timing/pull/85 - fix a small bug in the example (by siusin) https://github.com/w3c/resource-timing/pull/84 - clarify responseStart (by igrigorik) https://github.com/w3c/resource-timing/pull/83 6 pull requests merged: - Typo fix https://github.com/w3c/resource-timing/pull/86 - s/MUST/MAY semantics for failed fetches in L2 https://github.com/w3c/resource-timing/pull/85 - fix a small bug in the example https://github.com/w3c/resource-timing/pull/84 - Recommendation for when add/queue steps should run https://github.com/w3c/resource-timing/pull/79 - updated timing attribute diagram https://github.com/w3c/resource-timing/pull/81 - Clarify initiatorType https://github.com/w3c/resource-timing/pull/80 6 pull requests received 10 new comments: - #83 clarify responseStart (4 by igrigorik, yoavweiss) https://github.com/w3c/resource-timing/pull/83 - #85 s/MUST/MAY semantics for failed fetches in L2 (2 by igrigorik, plehegar) https://github.com/w3c/resource-timing/pull/85 - #79 Recommendation for when add/queue steps should run (1 by igrigorik) https://github.com/w3c/resource-timing/pull/79 - #80 Clarify initiatorType (1 by nicjansma) https://github.com/w3c/resource-timing/pull/80 - #84 fix a small bug in the example (1 by igrigorik) https://github.com/w3c/resource-timing/pull/84 - #86 Typo fix (1 by igrigorik) https://github.com/w3c/resource-timing/pull/86 * w3c/navigation-timing (+0/-1/💬1) 1 pull requests merged: - updated timing attributes diagram https://github.com/w3c/navigation-timing/pull/52 1 pull requests received 1 new comments: - #52 updated timing attributes diagram (1 by toddreifsteck) https://github.com/w3c/navigation-timing/pull/52 * w3c/preload (+0/-1/💬1) 1 pull requests merged: - Response cache and matching lives in Fetch https://github.com/w3c/preload/pull/79 1 pull requests received 1 new comments: - #79 Response cache and matching lives in Fetch (1 by yoavweiss) https://github.com/w3c/preload/pull/79 * w3c/requestidlecallback (+1/-0/💬0) 1 pull requests submitted: - Incorporate feedback (by igrigorik) https://github.com/w3c/requestidlecallback/pull/50 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, 6 December 2016 17:00:20 UTC