W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2017

Weekly github digest (Web Performance WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 14 Nov 2017 17:00:17 +0000
To: public-web-perf@w3.org
Message-Id: <E1eEeZN-00033f-97@uranus.w3.org>



Issues
------
* w3c/resource-timing (+2/-0/💬18)
  2 issues created:
  - Clarify relationship between `onload`, adding entries and their completeness (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/127
  - Review that Resource Timing 2 language works for QUIC (by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/126

  9 issues received 18 new comments:
  - #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (4 by mattto, wanderview)
    https://github.com/w3c/resource-timing/issues/119
  - #122 NextHopProtocol Values (4 by RyanAtGoogle, sleevi, plehegar, toddreifsteck)
    https://github.com/w3c/resource-timing/issues/122
  - #120 TFO and secureConnectionStart (3 by rniwa, toddreifsteck)
    https://github.com/w3c/resource-timing/issues/120
  - #100 Clarify what constitutes a "downloadable resource" (2 by JosephPecoraro, toddreifsteck)
    https://github.com/w3c/resource-timing/issues/100
  - #87 Ensure that first byte measurement and 1XX responses are covered by tests (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/87
  - #110 InitiatorType of service worker navigation preload (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/110
  - #89 Increase limit of 150 for PerformanceEntrys? (1 by jjinux)
    https://github.com/w3c/resource-timing/issues/89
  - #123 how do dns and connectStart handle multiple ip/name options? (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/123
  - #93 Determine whether to wait until after responseEnd to queue entry for ResourceTiming (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/93

* w3c/navigation-timing (+2/-0/💬0)
  2 issues created:
  - Timings for beforeUnload event (by andydavies)
    https://github.com/w3c/navigation-timing/issues/79
  - Should processing model cut the steps defined by PerformanceResourceTiming? (by toddreifsteck)
    https://github.com/w3c/navigation-timing/issues/78

* w3c/page-visibility (+0/-0/💬3)
  1 issues received 3 new comments:
  - #34 It is unclear in PR whether UA may mark hidden when obscured (3 by toddreifsteck)
    https://github.com/w3c/page-visibility/issues/34

* w3c/resource-hints (+1/-0/💬2)
  1 issues created:
  - Hinting HTTP Alternative Services (by LPardue)
    https://github.com/w3c/resource-hints/issues/72

  1 issues received 2 new comments:
  - #67 Transition Level 1 to CR (2 by toddreifsteck)
    https://github.com/w3c/resource-hints/issues/67

* w3c/requestidlecallback (+1/-0/💬7)
  1 issues created:
  - "deadline" in the "start an idle period algorithm" should be defined in terms of event loop (by rniwa)
    https://github.com/w3c/requestidlecallback/issues/71

  2 issues received 7 new comments:
  - #70 Missing definition for "idle time" (5 by toddreifsteck, igrigorik, rmcilroy, domenic)
    https://github.com/w3c/requestidlecallback/issues/70
  - #71 "deadline" in the "start an idle period algorithm" should be defined in terms of event loop (2 by rniwa, rmcilroy)
    https://github.com/w3c/requestidlecallback/issues/71

* w3c/server-timing (+0/-0/💬8)
  3 issues received 8 new comments:
  - #40 Consider shorter names for the attributes (4 by cvazac, mnot, yoavweiss, achristensen07)
    https://github.com/w3c/server-timing/issues/40
  - #39 Future considerations (3 by sroussey, cvazac, kbrock)
    https://github.com/w3c/server-timing/issues/39
  - #38 RT and NT processing is not well defined (1 by siusin)
    https://github.com/w3c/server-timing/issues/38



Pull requests
-------------
* w3c/resource-timing (+1/-0/💬1)
  1 pull requests submitted:
  - V2 (by DharshanJS)
    https://github.com/w3c/resource-timing/pull/128

  1 pull requests received 1 new comments:
  - #128 V2 (1 by plehegar)
    https://github.com/w3c/resource-timing/pull/128

* w3c/page-visibility (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #33 fix broken links (1 by marcoscaceres)
    https://github.com/w3c/page-visibility/pull/33

* w3c/paint-timing (+1/-0/💬0)
  1 pull requests submitted:
  - Use sentence case in headers (by npm1)
    https://github.com/w3c/paint-timing/pull/21


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, 14 November 2017 17:00:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 November 2017 17:00:24 UTC