W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2018

Re: Minimal event timing proposal

From: Ilya Grigorik <igrigorik@google.com>
Date: Fri, 16 Feb 2018 10:43:08 -0800
Message-ID: <CADXXVKrz6D6-0+hW092v9dS-EWTB4X3x=FCQi8eGmSRCy95rDg@mail.gmail.com>
To: Timothy Dresser <tdresser@chromium.org>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
Tim, thanks for drafting this! I like where this is headed.

Left a few questions in the doc and added this to our agenda for next
design call
<https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit#heading=h.ljsbtcikd3cl>
(date
TBD).

On Thu, Feb 15, 2018 at 1:53 PM, Timothy Dresser <tdresser@chromium.org>
wrote:

> Based on our discussion on First Input Delay
> <https://docs.google.com/document/d/1Tnobrn4I8ObzreIztfah_BYnDkbx3_ZfJV5gj2nrYnY/edit> at
> the last WG meeting, I've put together a minimal proposal
> <https://docs.google.com/document/d/10CdRCrUQzQF1sk8uHmhEPG7F_jcZ2S3l9Zm40lp3qYk/edit#heading=h.fbdd8nwxr7v4> for
> an event timing API.
>
> The extensions to the DOM spec are fairly straight forward, and the API
> itself is pretty bare bones. The main question is whether or not
> dispatching an entry per DOM event is too expensive.
>
> If it is, we'll need to devise a method to only report a subset of events.
>
> I'd appreciate any feedback you have,
> Tim
>
Received on Friday, 16 February 2018 18:44:13 UTC

This archive was generated by hypermail 2.3.1 : Friday, 16 February 2018 18:44:13 UTC