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

Weekly github digest (Web Performance WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 19 Jun 2018 17:00:44 +0000
To: public-web-perf@w3.org
Message-Id: <E1fVJzo-0000zY-0x@uranus.w3.org>



Issues
------
* w3c/resource-timing (+0/-1/💬24)
  6 issues received 24 new comments:
  - #122 NextHopProtocol Values (13 by RyanAtGoogle, igrigorik, yoavweiss, LPardue, MikeBishop)
    https://github.com/w3c/resource-timing/issues/122 [Clarification] 
  - #82 Clarify when entry is added to performance entry buffer (4 by npm1, yoavweiss)
    https://github.com/w3c/resource-timing/issues/82 [Clarification] [discuss_180618] [needs tests] 
  - #141 When is resourcetimingbufferfull supposed to fire? (3 by smaug----, npm1, yoavweiss)
    https://github.com/w3c/resource-timing/issues/141 [Clarification] [discuss_180618] 
  - #96 Clarify behavior of setResourceTimingBufferSize (2 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/96 [test:missing-coverage] 
  - #100 Clarify what constitutes a "downloadable resource" (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/100 [Clarification] [needs tests] 
  - #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (1 by mattto)
    https://github.com/w3c/resource-timing/issues/119 [Clarification] [needs tests] 

  1 issues closed:
  - NextHopProtocol Values https://github.com/w3c/resource-timing/issues/122 [Clarification] 

* w3c/paint-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #29 Clarify invisible text (1 by irori)
    https://github.com/w3c/paint-timing/issues/29 

* w3c/longtasks (+1/-0/💬0)
  1 issues created:
  - Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? (by npm1)
    https://github.com/w3c/longtasks/issues/41 



Pull requests
-------------
* w3c/performance-timeline (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #102 Update web-platform-tests URL (1 by igrigorik)
    https://github.com/w3c/performance-timeline/pull/102 

  1 pull requests merged:
  - Update web-platform-tests URL
    https://github.com/w3c/performance-timeline/pull/102 

* w3c/resource-timing (+0/-1/💬5)
  2 pull requests received 5 new comments:
  - #159 Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC (4 by yoavweiss, LPardue)
    https://github.com/w3c/resource-timing/pull/159 
  - #158 Remove the restriction for no-cors CSS subresources (1 by yoavweiss)
    https://github.com/w3c/resource-timing/pull/158 

  1 pull requests merged:
  - Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC
    https://github.com/w3c/resource-timing/pull/159 

* w3c/preload (+1/-1/💬1)
  1 pull requests submitted:
  - editorial: enable caniuse (by sidvishnoi)
    https://github.com/w3c/preload/pull/124 

  1 pull requests received 1 new comments:
  - #124 editorial: enable caniuse (1 by igrigorik)
    https://github.com/w3c/preload/pull/124 

  1 pull requests merged:
  - editorial: enable caniuse
    https://github.com/w3c/preload/pull/124 


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, 19 June 2018 17:00:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 19 June 2018 17:00:47 UTC