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

Issues
------
* w3c/navigation-timing (+0/-1/💬4)
  1 issues closed:
  - [Maintenance, reminder] Cycle environment variables that were 
encrypted with Travis 
https://github.com/w3c/navigation-timing/issues/51

  3 issues received 4 new comments:
  - #50 data bias issues due to deferring reporting of all nav timing 
metrics to the load event (2 by igrigorik, bluesmoon)
    https://github.com/w3c/navigation-timing/issues/50
  - #44 Processing Model chart is missing domLoading marker (1 by 
igrigorik)
    https://github.com/w3c/navigation-timing/issues/44
  - #51 [Maintenance, reminder] Cycle environment variables that were 
encrypted with Travis (1 by igrigorik)
    https://github.com/w3c/navigation-timing/issues/51

* w3c/preload (+1/-2/💬5)
  1 issues created:
  - Require "as" attribute (by AshleyScirra)
    https://github.com/w3c/preload/issues/80

  2 issues closed:
  - Load event scheduling https://github.com/w3c/preload/issues/69
  - [Maintenance, reminder] Cycle environment variables that were 
encrypted with Travis https://github.com/w3c/preload/issues/78

  2 issues received 5 new comments:
  - #69 Load event scheduling (4 by igrigorik, yoavweiss)
    https://github.com/w3c/preload/issues/69
  - #78 [Maintenance, reminder] Cycle environment variables that were 
encrypted with Travis (1 by igrigorik)
    https://github.com/w3c/preload/issues/78

* w3c/requestidlecallback (+0/-1/💬12)
  1 issues closed:
  - implementations should be allowed to consider work beyond "other 
event loops" https://github.com/w3c/requestidlecallback/issues/46

  6 issues received 12 new comments:
  - #47 It is unclear what IdleDeadline.timeRemaining()  should return
 if JS keeps the IdleDealing object alive even after the callback 
call. (4 by igrigorik, rmcilroy, bzbarsky)
    https://github.com/w3c/requestidlecallback/issues/47
  - #42 When/how could 50 ms chunks of time occur vs. typical 
frame-based 16 ms? (2 by igrigorik, rmcilroy)
    https://github.com/w3c/requestidlecallback/issues/42
  - #44 diagram with frame commit and vsync is inaccurate for some 
browsers (2 by igrigorik, rmcilroy)
    https://github.com/w3c/requestidlecallback/issues/44
  - #45 Use push/pop or append/take-the-first (2 by igrigorik, 
rmcilroy)
    https://github.com/w3c/requestidlecallback/issues/45
  - #41 Improve the specification of how requestIdleCallback events 
are ordered (1 by igrigorik)
    https://github.com/w3c/requestidlecallback/issues/41
  - #43 What should occur if requestIdleCallback backs up? (1 by 
igrigorik)
    https://github.com/w3c/requestidlecallback/issues/43


Pull requests
-------------
* w3c/navigation-timing (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #52 updated timing attributes diagram (1 by yoavweiss)
    https://github.com/w3c/navigation-timing/pull/52

* w3c/preload (+1/-0/💬0)
  1 pull requests submitted:
  - Response cache and matching lives in Fetch (by igrigorik)
    https://github.com/w3c/preload/pull/79


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, 29 November 2016 17:00:15 UTC