W3C home > Mailing lists > Public > public-web-perf@w3.org > January 2018

Weekly github digest (Web Performance WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 30 Jan 2018 17:00:30 +0000
To: public-web-perf@w3.org
Message-Id: <E1egZGo-0003yz-TZ@uranus.w3.org>



Issues
------
* w3c/resource-timing (+3/-1/💬12)
  3 issues created:
  - `resourcetimingbufferfull` should fire at the `Performance` EventTarget (by mnoorenberghe)
    https://github.com/w3c/resource-timing/issues/143
  - `InitiatorType` should not single out XHR (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/142
  - When is resourcetimingbufferfull supposed to fire? (by smaug----)
    https://github.com/w3c/resource-timing/issues/141

  6 issues received 12 new comments:
  - #138 initiatorType test cases (3 by annevk, yoavweiss)
    https://github.com/w3c/resource-timing/issues/138
  - #141 When is resourcetimingbufferfull supposed to fire? (3 by igrigorik, smaug----)
    https://github.com/w3c/resource-timing/issues/141
  - #133 Resource processing time (2 by colinbendell, tdresser)
    https://github.com/w3c/resource-timing/issues/133
  - #142 `InitiatorType` should not single out XHR (2 by annevk)
    https://github.com/w3c/resource-timing/issues/142
  - #137 Proposal: API for exposing resource requests (1 by npm1)
    https://github.com/w3c/resource-timing/issues/137
  - #143 `resourcetimingbufferfull` should fire at the `Performance` EventTarget (1 by mnoorenberghe)
    https://github.com/w3c/resource-timing/issues/143

  1 issues closed:
  - `resourcetimingbufferfull` should fire at the `Performance` EventTarget https://github.com/w3c/resource-timing/issues/143

* w3c/preload (+1/-0/💬0)
  1 issues created:
  - RFC 5988 was silently obsoleted by RFC 8288 (by mdocguard)
    https://github.com/w3c/preload/issues/119

* w3c/resource-hints (+0/-0/💬2)
  1 issues received 2 new comments:
  - #77 Recursive prefetch or similar-origin prerender (2 by yoavweiss, cramforce)
    https://github.com/w3c/resource-hints/issues/77

* w3c/paint-timing (+0/-0/💬6)
  1 issues received 6 new comments:
  - #28 [Question]Some questions about the spec (6 by tdresser, NE-SmallTown)
    https://github.com/w3c/paint-timing/issues/28



Pull requests
-------------
* w3c/resource-timing (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #135 Fix respec issues (1 by siusin)
    https://github.com/w3c/resource-timing/pull/135

  1 pull requests merged:
  - Fix respec issues
    https://github.com/w3c/resource-timing/pull/135

* w3c/user-timing (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #35 Address outstanding L2 issues (1 by philipwalton)
    https://github.com/w3c/user-timing/pull/35


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, 30 January 2018 17:01:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 30 January 2018 17:01:13 UTC