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

I guess point 20.1 in 5.1 (Processing Model) could be interpreted as the option you are proposing, i.e. invoking clearResourceTimings doesn't clear the primary buffer immediately but it just sets a flag which would cause the buffer to be cleared after the event is processed.

If that's the desired behaviour I think it should be documented both in 5.1/20.1 and in 4.4/clearResourceTimings, right?

Another option is to not extend EventTarget, but I don't have a strong sense about the correctness of that one :)

-JC

________________________________
From: James Simonsen [simonjam@google.com]
Sent: October 2, 2013 2:13 PM
To: Juan Carlos Estibariz
Cc: public-web-perf@w3.org
Subject: Re: [ResourceTiming] Handling of "resourcetimingbufferfull" events makes no sense

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?

James


On Tue, Oct 1, 2013 at 9:46 AM, Juan Carlos Estibariz <Juan.Carlos.Estibariz@software.dell.com<mailto: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