W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2012

Re: DOMHighResTimeStamps in DOM events, use cases

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 9 Oct 2012 13:41:22 +0200
Message-ID: <CADnb78jgrMuksz9hNswCcUPoOavt=Lh-udUwW+zWzGSk=uybHw@mail.gmail.com>
To: Robert Flack <flackr@chromium.org>
Cc: www-dom@w3.org
On Fri, Oct 5, 2012 at 7:03 PM, Robert Flack <flackr@chromium.org> wrote:
> I've implemented a webkitHRTimeStamp attribute to DOM events in
> https://bugs.webkit.org/show_bug.cgi?id=94987 consistent with the
> Performance API timestamps which uses the raw timestamp from the received
> PlatformEvent. I and a couple of others here have patched this in to do
> performance benchmarks of event delivery. Using the platform event timestamp
> has been especially advantageous as it's generated when the kernel receives
> the event, rather than the timestamp property which gives the time of the
> DOM Event object creation.

Would it break too much to simply update timeStamp and make it work
like this? And have it return DOMHighResTimeStamp?

Received on Tuesday, 9 October 2012 11:41:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:01 UTC