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, 20 Dec 2016 17:00:07 +0000
To: public-web-perf@w3.org
Message-Id: <E1cJNln-0005oq-Kv@uranus.w3.org>


Issues
------
* w3c/resource-timing (+2/-1/💬1)
  2 issues created:
  - Resource Timing entries within the context of a service worker for
 handled requests? (by KenjiBaheux)
    https://github.com/w3c/resource-timing/issues/88
  - Ensure that first byte measurement and 1XX responses are covered 
by tests (by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/87

  1 issues closed:
  - Clarify definition of responseStart 
https://github.com/w3c/resource-timing/issues/63

  1 issues received 1 new comments:
  - #63 Clarify definition of responseStart (1 by igrigorik)
    https://github.com/w3c/resource-timing/issues/63

* w3c/navigation-timing (+2/-1/💬3)
  2 issues created:
  - Report URL in "name" attribute (instead of "document") (by 
spanicker)
    https://github.com/w3c/navigation-timing/issues/59
  - Need tests for TAO (by toddreifsteck)
    https://github.com/w3c/navigation-timing/issues/58

  1 issues closed:
  - Automatic publication of the spec fails due to markup errors 
https://github.com/w3c/navigation-timing/issues/57

  2 issues received 3 new comments:
  - #57 Automatic publication of the spec fails due to markup errors 
(2 by plehegar)
    https://github.com/w3c/navigation-timing/issues/57
  - #59 Report URL in "name" attribute (instead of "document") (1 by 
igrigorik)
    https://github.com/w3c/navigation-timing/issues/59

* w3c/user-timing (+2/-0/💬2)
  2 issues created:
  - What does "navigationStart" mean as a second argument to 
performance.measure() in a web worker? (by plehegar)
    https://github.com/w3c/user-timing/issues/22
  - measure() may throw SyntaxError (by plehegar)
    https://github.com/w3c/user-timing/issues/21

  1 issues received 2 new comments:
  - #15 Enable association with input events. (2 by nolanlawson, 
tdresser)
    https://github.com/w3c/user-timing/issues/15

* w3c/beacon (+0/-0/💬1)
  1 issues received 1 new comments:
  - #38 Ambiguity on "maximum data size" limit and enforcement (1 by 
andrewwakeling)
    https://github.com/w3c/beacon/issues/38

* w3c/preload (+1/-0/💬29)
  1 issues created:
  - Define resource abortion when link element or `rel` are removed  
(by yoavweiss)
    https://github.com/w3c/preload/issues/82

  3 issues received 29 new comments:
  - #80 Require "as" attribute (22 by igrigorik, MarcoHengstenberg, 
zcorpan, annevk, simevidas, sideshowbarker, yoavweiss, mems, 
AshleyScirra)
    https://github.com/w3c/preload/issues/80
  - #82 Define resource abortion when link element or `rel` are 
removed  (4 by igrigorik, yoavweiss)
    https://github.com/w3c/preload/issues/82
  - #81 Explain rel=preload in terms of Fetch (3 by igrigorik, annevk)
    https://github.com/w3c/preload/issues/81

* w3c/requestidlecallback (+0/-5/💬7)
  5 issues closed:
  - What should occur if requestIdleCallback backs up? 
https://github.com/w3c/requestidlecallback/issues/43
  - Improve the specification of how requestIdleCallback events are 
ordered https://github.com/w3c/requestidlecallback/issues/41
  - When/how could 50 ms chunks of time occur vs. typical frame-based 
16 ms? https://github.com/w3c/requestidlecallback/issues/42
  - Use push/pop or append/take-the-first 
https://github.com/w3c/requestidlecallback/issues/45
  - It is unclear what IdleDeadline.timeRemaining()  should return if 
JS keeps the IdleDealing object alive even after the callback call. 
https://github.com/w3c/requestidlecallback/issues/47

  2 issues received 7 new comments:
  - #44 diagram with frame commit and vsync is inaccurate for some 
browsers (6 by igrigorik, rmcilroy, toddreifsteck)
    https://github.com/w3c/requestidlecallback/issues/44
  - #43 What should occur if requestIdleCallback backs up? (1 by 
toddreifsteck)
    https://github.com/w3c/requestidlecallback/issues/43


Pull requests
-------------
* w3c/resource-timing (+0/-1/💬1)
  1 pull requests merged:
  - clarify responseStart
    https://github.com/w3c/resource-timing/pull/83

  1 pull requests received 1 new comments:
  - #83 clarify responseStart (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/pull/83

* w3c/navigation-timing (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #55 apply TAO check (1 by toddreifsteck)
    https://github.com/w3c/navigation-timing/pull/55

* w3c/beacon (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #39 (WIP) Enforce payload limits via Fetch API (1 by 
andrewwakeling)
    https://github.com/w3c/beacon/pull/39

* w3c/requestidlecallback (+0/-1/💬1)
  1 pull requests merged:
  - Incorporate feedback
    https://github.com/w3c/requestidlecallback/pull/50

  1 pull requests received 1 new comments:
  - #50 Incorporate feedback (1 by toddreifsteck)
    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, 20 December 2016 17:00:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 December 2016 17:00:14 UTC