Hi all. As a heads up, a couple of issues we're iterating on based on feedback from Matt Woodrow / Robert O'Callahan (Mozilla): - Expose cpuTime on compositor + mainframe events: https://github.com/GoogleChrome/websmoothness/issues/17 - Capturing frame duration, omit zero values: https://github.com/GoogleChrome/websmoothness/issues/18 - Constraints on returned events via getEntriesByType: https://github.com/GoogleChrome/websmoothness/issues/19 If you have any feedback / suggestions / questions.. let us know! ig On Tue, Oct 7, 2014 at 2:04 PM, Michael Blain <mpb@google.com> wrote: > Hi Web Perf, > > Based on some of the feedback we got on my last thread ( > http://lists.w3.org/Archives/Public/public-web-perf/2014Sep/0040.html), > we put together a proposed spec (and document explaining the motivation/how > this API would be used) here: > > https://github.com/GoogleChrome/websmoothness/wiki/Explainer > > https://rawgit.com/GoogleChrome/websmoothness/master/spec/index.html > > We have a CL that implements the proposed API (or very close to it) but > are looking for some feedback from the community/other vendors of exposing > the same data on other platforms. > > We'd love for this to be part of the webperf group mandate. Any objections > to bringing it up on an upcoming conference call and at TPAC? > > Thanks! >  > Michael Blain > mpb@google.com >
Received on Monday, 13 October 2014 20:55:23 UTC