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

Issues
------
* w3c/hr-time (+2/-1/💬4)
  2 issues created:
  - Time Origin in Workers - official moment of creation or not? (by 
JosephPecoraro)
    https://github.com/w3c/hr-time/issues/41
  - Why is `Performance` an `EventTarget`? (by JosephPecoraro)
    https://github.com/w3c/hr-time/issues/40

  1 issues closed:
  - Why is Performance an EventTarget? 
https://github.com/w3c/hr-time/issues/40

  2 issues received 4 new comments:
  - #40 Why is Performance an EventTarget? (2 by igrigorik, 
JosephPecoraro)
    https://github.com/w3c/hr-time/issues/40
  - #41 Time Origin in Workers - official moment of creation or not? 
(2 by igrigorik, JosephPecoraro)
    https://github.com/w3c/hr-time/issues/41

* w3c/performance-timeline (+3/-0/💬2)
  3 issues created:
  - Clarify sort order for entries with equivalent startTime (by 
JosephPecoraro)
    https://github.com/w3c/performance-timeline/issues/67
  - Clarify disconnecting a PerformanceObserver that has observed 
entries (by JosephPecoraro)
    https://github.com/w3c/performance-timeline/issues/66
  - Clarify how PerformanceObserver invokes the callback - arguments 
and `this` value (by JosephPecoraro)
    https://github.com/w3c/performance-timeline/issues/65

  2 issues received 2 new comments:
  - #66 Clarify disconnecting a PerformanceObserver that has observed 
entries (1 by JosephPecoraro)
    https://github.com/w3c/performance-timeline/issues/66
  - #67 Clarify sort order for entries with equivalent startTime (1 by
 JosephPecoraro)
    https://github.com/w3c/performance-timeline/issues/67

* w3c/resource-timing (+1/-1/💬4)
  1 issues created:
  - Clarify whether UA can clear the buffer under memory pressure (by 
spanicker)
    https://github.com/w3c/resource-timing/issues/94

  1 issues closed:
  - mark() and measure() return PerformanceEntries 
https://github.com/w3c/resource-timing/issues/91

  3 issues received 4 new comments:
  - #94 Clarify whether UA can clear the buffer under memory pressure 
(2 by n8schloss, yoavweiss)
    https://github.com/w3c/resource-timing/issues/94
  - #89 Increase limit of 150 for PerformanceEntrys? (1 by igrigorik)
    https://github.com/w3c/resource-timing/issues/89
  - #91 mark() and measure() return PerformanceEntries (1 by 
toddreifsteck)
    https://github.com/w3c/resource-timing/issues/91

* w3c/user-timing (+1/-0/💬0)
  1 issues created:
  - mark() and measure() return PerformanceEntries (by toddreifsteck)
    https://github.com/w3c/user-timing/issues/23

* w3c/beacon (+2/-0/💬0)
  2 issues created:
  - Tests for CORS and sendBeacon() (by annevk)
    https://github.com/w3c/beacon/issues/41
  - ArrayBuffer uses "application/octet-stream" as default 
Content-Type in impl (by annevk)
    https://github.com/w3c/beacon/issues/40

* w3c/preload (+1/-0/💬0)
  1 issues created:
  - Difference between Link: rel=preload header and the link HTML 
element (by pelchats)
    https://github.com/w3c/preload/issues/84

* w3c/resource-hints (+0/-0/💬14)
  2 issues received 14 new comments:
  - #70 Why are prefetch links optionally blockable instead of 
blockable? (12 by igrigorik, mikewest, yoavweiss, bzbarsky, dveditz)
    https://github.com/w3c/resource-hints/issues/70
  - #67 Transition Level 1 to CR (2 by yoavweiss, myakura)
    https://github.com/w3c/resource-hints/issues/67




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, 31 January 2017 17:00:26 UTC