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

Intent to Migrate (WICG → WebPerf WG): Long Tasks API and Server Timing

From: Ilya Grigorik <igrigorik@google.com>
Date: Thu, 23 Mar 2017 12:31:15 -0700
Message-ID: <CADXXVKrXNVj1BxuiwsA+sMwNMTdkxSArbDwoL_9aLn+BSL4R-w@mail.gmail.com>
To: public-web-perf <public-web-perf@w3.org>
Cc: Todd Reifsteck <toddreif@microsoft.com>, Philippe Le Hegaret <plh@w3.org>, Yoav Weiss <yoav@yoav.ws>, Chris Wilson <cwilso@google.com>, Marcos Caceres <w3c@marcosc.com>
tl;dr: we are migrating Long Tasks and Server Timing proposals from WICG to
WebPerf WG.

*# Long Tasks API *
Spec: https://github.com/wicg/longtask
Editors: panicker@chromium.org, domenic@chromium.org, igrigorik@chromium.org

Long Tasks API was incubated in WICG and the group has been involved from
the start: we discussed it at length at TPAC and been iterating on it
since, in our calls and via WICG discussions. Chrome is shipping v1 of the
API soon
We intend to migrate and continue work on this spec within WebPerf WG.

*# Server Timing*
Spec: https://github.com/wicg/server-timing
Editors: cvazac@akamai.com, yweiss@akamai.com, igrigorik@chromium.org

Server Timing was originally incubated in WebPerf WG and later migrated to
WICG because implementer interest was unclear. More recently, it has been
integrated into Chrome DevTools and there is a Blink intent to implement
We intend to migrate the spec back to WebPerf WG and resume work on it:
rebase it to integrate with PerformanceObserver, etc.


Both of the above are in scope of the group charter. Related minutes from
WG call:
Received on Thursday, 23 March 2017 19:32:29 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 March 2017 19:32:29 UTC