- From: Nicolás Peña <npm@google.com>
- Date: Fri, 26 Jan 2018 11:47:53 -0500
- To: Ilya Grigorik <igrigorik@google.com>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Friday, 26 January 2018 16:48:39 UTC
Either of those times work for me. No preference. On Fri, Jan 26, 2018 at 1:12 AM, Ilya Grigorik <igrigorik@google.com> wrote: > Hi Nicolás. Added this to our next WG design review call agenda [1]. The > exact time+date for that is TBD; can you ptal at [2] and see if either of > those work better for you? > > thanks! > > [1] https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B > 4q8Q46LMM/edit#heading=h.rpl2b9icihph > [2] https://lists.w3.org/Archives/Public/public-web-perf/2018Jan/0035.html > > On Thu, Jan 11, 2018 at 3:24 PM, Nicolás Peña <npm@google.com> wrote: > >> We would like to discuss a Chromium proposal to expose in-flight resource >> requests to developers via an API very similar to the current >> PerformanceResourceTiming. The GitHub issue is: >> >> https://github.com/w3c/resource-timing/issues/137 >> >> Does this look reasonable to other browser vendors? >> > >
Received on Friday, 26 January 2018 16:48:39 UTC