Re: Implementing the web timing spec

Rob Campbell <[email protected]>
Newsgroups gmane.comp.mozilla.devel.dom
Organization http://groups.google.com
Message-ID <02573830-6e0f-4eb2-a482-e48c2c87155d@v25g2000yqk.googlegroups.com>
On Feb 11, 2:28 pm, Christian Biesinger <[email protected]> wrote:
> Hi everyone,
>
> there's a specification for exposing detailed timing information of web
> page elements via the DOM:http://dev.w3.org/2006/webapi/WebTiming/
>
> Some people here would like to implement it in Firefox. The reason for
> exposing it via the DOM is to gather actual concrete end-user timings;
> other approaches don't allow that (also not all of this timing data is
> currently available to extensions).

I was looking at this a couple of weeks ago. I think blizzard pointed
me to it. A standardized mechanism for timing could be a great thing.

> The idea is to change the spec a bit to limit the number of elements on
> which this data is exposed, probably to drop the Ticks interface, etc.
>
> Would people agree this is useful, and in particular, would the DOM
> peers be willing to accept patches to implement this spec?

Has anyone filed a meta bug to capture implementation of these pieces
yet, assuming we do this? I think we should.

>
> Chromium is implementing this spec as well
> (https://lists.webkit.org/pipermail/webkit-dev/2009-October/010382.html).
> For a bit of discussion on the spec, see the thread at
> http://www.mail-archive.com/[email protected]/msg07393.html
>
> -christian
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.