W3C home > Mailing lists > Public > public-web-perf@w3.org > July 2012

RE: [Resource Timing] Spec feedback

From: Karen Anderson (IE) <Karen.Anderson@microsoft.com>
Date: Thu, 19 Jul 2012 18:07:57 +0000
To: James Simonsen <simonjam@chromium.org>, public-web-perf <public-web-perf@w3.org>
Message-ID: <748A9FD1BD28E74F971C8D69F63494720309D2F7@BL2PRD0310MB350.namprd03.prod.outlook.com>
I agree.  Firing the callback onresourcetimingbufferful immediately after adding a resource which puts the buffer at capacity makes sense.  It gives the developer (potentially) time to react proactively.


From: simonjam@google.com [mailto:simonjam@google.com] On Behalf Of James Simonsen
Sent: Wednesday, July 11, 2012 5:29 PM
To: public-web-perf
Subject: Re: [Resource Timing] Spec feedback

On Thu, Aug 18, 2011 at 12:52 PM, James Simonsen <simonjam@chromium.org<mailto:simonjam@chromium.org>> wrote:
"The callback onresourcetimingbufferfull is triggered when the buffer used to store the list of PerformanceResourceTiming is full"

  *   This should be more tightly defined: "The callback onresourcetimingbufferfull is called immediately after a resource is added to the buffer if the buffer size now equals the capacity." Or something along those lines.
  *   It's not immediately clear from reading the text, but I think the intent is that this only fires once when the buffer becomes full and not for every resource loaded after that. We shouldn't spam developers with events if they don't care about Resource Timing.
Sorry to revive this thread. What was the verdict on these points? The spec looks unchanged to me. It's still not clear exactly when and how often to fire the event.

My opinion is the same: I think it should be fired once immediately after the buffer becomes full.

Received on Thursday, 19 July 2012 18:09:16 UTC

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