W3C home > Mailing lists > Public > public-web-perf@w3.org > December 2016

Weekly digest of github activity (hr-time, performance-timeline, resource-timing, navigation-timing, user-timing, beacon, page-visibility, preload, resource-hints, requestidlecallback)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 27 Dec 2016 17:00:06 +0000
To: public-web-perf@w3.org
Message-Id: <E1cLv6c-0000gx-3A@uranus.w3.org>


Issues
------
* w3c/performance-timeline (+0/-0/💬1)
  1 issues received 1 new comments:
  - #56 Ability to observers past set of performance entries (1 by 
igrigorik)
    https://github.com/w3c/performance-timeline/issues/56

* w3c/resource-timing (+0/-0/💬5)
  3 issues received 5 new comments:
  - #88 Resource Timing entries within the context of a service worker
 for handled requests? (2 by igrigorik, wanderview)
    https://github.com/w3c/resource-timing/issues/88
  - #22 RT should tell about the failed request and http status code. 
(2 by igrigorik, vaibhavtripathi)
    https://github.com/w3c/resource-timing/issues/22
  - #71 Transition Level 2 to CR (1 by huynhhaiof)
    https://github.com/w3c/resource-timing/issues/71

* w3c/navigation-timing (+0/-1/💬2)
  1 issues closed:
  - Contribute tests for navigation timing 
https://github.com/w3c/navigation-timing/issues/39

  2 issues received 2 new comments:
  - #50 data bias issues due to deferring reporting of all nav timing 
metrics to the load event (1 by igrigorik)
    https://github.com/w3c/navigation-timing/issues/50
  - #39 Contribute tests for navigation timing (1 by igrigorik)
    https://github.com/w3c/navigation-timing/issues/39

* w3c/user-timing (+0/-0/💬5)
  1 issues received 5 new comments:
  - #22 What does "navigationStart" mean as a second argument to 
performance.measure() in a web worker? (5 by igrigorik, toddreifsteck,
 bzbarsky, nicjansma)
    https://github.com/w3c/user-timing/issues/22

* w3c/beacon (+0/-1/💬2)
  1 issues closed:
  - Need to add tests for sendBeacon 
https://github.com/w3c/beacon/issues/29

  2 issues received 2 new comments:
  - #29 Need to add tests for sendBeacon (1 by igrigorik)
    https://github.com/w3c/beacon/issues/29
  - #38 Ambiguity on "maximum data size" limit and enforcement (1 by 
igrigorik)
    https://github.com/w3c/beacon/issues/38

* w3c/preload (+0/-0/💬5)
  1 issues received 5 new comments:
  - #80 Require "as" attribute (5 by igrigorik, annevk, AshleyScirra)
    https://github.com/w3c/preload/issues/80

* w3c/requestidlecallback (+1/-2/💬6)
  1 issues created:
  - Images not found for w3.org (by Krinkle)
    https://github.com/w3c/requestidlecallback/issues/51

  2 issues closed:
  - Integration with IntersectionObserver 
https://github.com/w3c/requestidlecallback/issues/36
  - Images not found for w3.org 
https://github.com/w3c/requestidlecallback/issues/51

  4 issues received 6 new comments:
  - #44 diagram with frame commit and vsync is inaccurate for some 
browsers (3 by igrigorik, toddreifsteck)
    https://github.com/w3c/requestidlecallback/issues/44
  - #48 Transition Level 1 to CR (1 by igrigorik)
    https://github.com/w3c/requestidlecallback/issues/48
  - #36 Integration with IntersectionObserver (1 by igrigorik)
    https://github.com/w3c/requestidlecallback/issues/36
  - #51 Images not found for w3.org (1 by siusin)
    https://github.com/w3c/requestidlecallback/issues/51


Pull requests
-------------

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, 27 December 2016 17:00:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 27 December 2016 17:00:12 UTC