W3C home > Mailing lists > Public > public-web-perf@w3.org > September 2017

Weekly github digest (Web Performance WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 05 Sep 2017 17:00:23 +0000
To: public-web-perf@w3.org
Message-Id: <E1dpHD5-0007kl-UG@uranus.w3.org>

Issues
------
* w3c/performance-timeline (+0/-0/💬6)
  2 issues received 6 new comments:
  - #86 "bubbles" flag for monitoring of all IFRAMEs (4 by igrigorik, tdresser, nicjansma)
    https://github.com/w3c/performance-timeline/issues/86
  - #85 Would like a precise way to map PerformanceTimings to FetchEvent (2 by igrigorik, annevk)
    https://github.com/w3c/performance-timeline/issues/85

* w3c/resource-timing (+1/-1/💬2)
  1 issues created:
  - domainLookupStart and domainLookupEnd during HTTP/2 Connection Reuse (by sajal)
    https://github.com/w3c/resource-timing/issues/116

  1 issues received 2 new comments:
  - #116 domainLookupStart and domainLookupEnd during HTTP/2 Connection Reuse (2 by igrigorik, sajal)
    https://github.com/w3c/resource-timing/issues/116

  1 issues closed:
  - domainLookupStart and domainLookupEnd during HTTP/2 Connection Reuse https://github.com/w3c/resource-timing/issues/116

* w3c/preload (+0/-4/💬12)
  3 issues received 12 new comments:
  - #66 Urgency hints (8 by mnot, yoavweiss)
    https://github.com/w3c/preload/issues/66
  - #97 Define the "Preload Cache" (3 by annevk, yoavweiss)
    https://github.com/w3c/preload/issues/97
  - #99 Revisit `rel=preload` as a push signal (1 by yoavweiss)
    https://github.com/w3c/preload/issues/99

  4 issues closed:
  - How do we fetch resources specified in `Link` headers? https://github.com/w3c/preload/issues/101
  - Define the "Preload Cache" https://github.com/w3c/preload/issues/97
  - Urgency hints https://github.com/w3c/preload/issues/66
  - Revisit `rel=preload` as a push signal https://github.com/w3c/preload/issues/99

* w3c/resource-hints (+0/-0/💬1)
  1 issues received 1 new comments:
  - #1 Resource Hints on non <link> elements (1 by chicheng)
    https://github.com/w3c/resource-hints/issues/1

* w3c/device-memory (+2/-0/💬0)
  2 issues created:
  - Should device memory be limited to what the UA can access? (by bzbarsky)
    https://github.com/w3c/device-memory/issues/13
  - Issue tracking link is wrong (by bzbarsky)
    https://github.com/w3c/device-memory/issues/12

* w3c/paint-timing (+0/-1/💬0)
  1 issues closed:
  - PerformanceTimeline or NavigationTiming support https://github.com/w3c/paint-timing/issues/6



Pull requests
-------------
* w3c/preload (+1/-1/💬0)
  1 pull requests submitted:
  - Clarify - Link header processing only happens after Document is created (by yoavweiss)
    https://github.com/w3c/preload/pull/110

  1 pull requests merged:
  - Clarify - Link header processing only happens after Document is created
    https://github.com/w3c/preload/pull/110

* w3c/paint-timing (+0/-1/💬0)
  1 pull requests merged:
  - Fix grammatical typo in README
    https://github.com/w3c/paint-timing/pull/3

* w3c/server-timing (+1/-0/💬0)
  1 pull requests submitted:
  - address w3ctag review feedback (by cvazac)
    https://github.com/w3c/server-timing/pull/31


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, 5 September 2017 17:00:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 September 2017 17:00:36 UTC