W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2017

RE: Delaying PerformanceEntry dispatch

From: Todd Reifsteck <toddreif@microsoft.com>
Date: Mon, 27 Nov 2017 18:39:52 +0000
To: Ben Kelly <bkelly@mozilla.com>, Timothy Dresser <tdresser@chromium.org>, Nic Jansma <njansma@soasta.com>, Yoav Weiss <yoav@yoav.ws>, Nathan Schloss <n8s@fb.com>
CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <MWHPR21MB0750CFECF0CC630D55F277E0C2250@MWHPR21MB0750.namprd21.prod.outlook.com>
My personal take is that this is good for performance, but I know there are use-cases on the web for pulling records from the Performance Timeline immediately.

I believe it was one of Nic, Yoav or Nate that previously mentioned this.


From: Ben Kelly [mailto:bkelly@mozilla.com]
Sent: Monday, November 27, 2017 7:24 AM
To: Timothy Dresser <tdresser@chromium.org>
Cc: public-web-perf@w3.org
Subject: Re: Delaying PerformanceEntry dispatch

On Mon, Nov 27, 2017 at 8:33 AM, Timothy Dresser <tdresser@chromium.org<mailto:tdresser@chromium.org>> wrote:
Any thoughts on whether this makes sense, and whether you're likely to add this delay?

I filed a bug to discuss it for firefox:


On face value it sounds reasonable to me as long as sites have not come to rely on immediate notification.  I'm not the primary owner of this feature in gecko, though.

Received on Monday, 27 November 2017 18:40:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 27 November 2017 18:40:26 UTC