Implementing the web timing spec

[Christian Biesinger]

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).

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?

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/public-...@w3.org/msg07393.html

-christian

[Christopher Blizzard]

Hey, I'm reviving this super-old thread. Christian, it looks like
you've been pretty active with others in this bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=570341

This is something that I think we're going to want to have, if you
need help let me know.

--Chris

> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>

[Christopher Blizzard]

And I just found the longer conversation in .dom.