W3C home > Mailing lists > Public > public-web-perf@w3.org > October 2013

Re: [ResourceTiming] Handling of "resourcetimingbufferfull" events makes no sense

From: James Simonsen <simonjam@google.com>
Date: Wed, 2 Oct 2013 11:13:50 -0700
Message-ID: <CAPVJQikyNMY86ogWXCGZsTOV=hcNNkS3Q_gPSsXS0iqsrRxN8A@mail.gmail.com>
To: Juan Carlos Estibariz <Juan.Carlos.Estibariz@software.dell.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
This is a good point. The simple function made it clear that there could
only be one.

We could address it by making clearResourceTimings async. Anyone else have
an opinion?


On Tue, Oct 1, 2013 at 9:46 AM, Juan Carlos Estibariz <
Juan.Carlos.Estibariz@software.dell.com> wrote:

> Hi,
> I just noticed this thread and I wanted to point out that since the
> handler of resourcetimingbufferfull is supposed to clear the buffer (so new
> entries can be added), having more than one handler for this event (by
> using addEventListener from EventTarget) is probably going to produce
> incorrect results for all but one of them.
> -JC
Received on Wednesday, 2 October 2013 18:14:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC