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

Re: API draft proposal: DOM Timing

From: Tim Dresser <tdresser@google.com>
Date: Tue, 12 Jun 2018 09:33:38 -0400
Message-ID: <CAHTsfZBrUBSe+OkmrFmvJYtDOK29whcWCHDsix1cwpjynRcn1A@mail.gmail.com>
To: Gilles Dubuc <gilles@wikimedia.org>
Cc: public-web-perf@w3.org
Hi Gilles!

This is the right forum for this. See the issue here
<https://github.com/w3c/charter-webperf/issues/30> for a bit of discussion.
Our most recent proposal is here
<https://docs.google.com/document/d/1sBM5lzDPws2mg1wRKiwM0TGFv9WqI6gEdF7vYhBYqUg/edit#heading=h.eny79fwwx642>,
but we've had some additional discussions since last updating the doc, and
plan to get a more formal explainer up fairly soon.

Our initial proposal involved specifying elements using CSS selectors, but
that's definitely too high overhead.
We're currently planning on pushing on registration via DOM attributes.

On Tue, Jun 12, 2018 at 9:24 AM Gilles Dubuc <gilles@wikimedia.org> wrote:

> Hi everyone,
>
> I've had a rough idea for what's at the top of my wishlist in terms of
> client-side performance APIs that don't exist yet, and turned it into this
> document:
> https://docs.google.com/document/d/1uClbE5oVGeChekv3VB5Zg3LNorU7VkfxHmNQdFxbP8M/edit?usp=sharing
>
> This working group seems like it could be a good place for this work to
> happen. For now I'm soliciting feedback on the idea itself. Maybe it's
> nonsensical, maybe it's too hard to implement. I think there are a lot of
> people here who could provide valuable opinions on it. Feel free to respond
> directly on the document or here.
>
> Also, let me know if this is the right venue to discuss this sort of thing
> or if there is a better place to discuss nascent web performance browser
> API proposals.
>
> Thanks,
> Gilles
>
Received on Tuesday, 12 June 2018 13:34:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 12 June 2018 13:34:17 UTC