Re: [webkit-dev] currentTime() and UTC time
I agree with the fact that it should not rely on currentTime() as it currently does. It is probably the root of bugs like https://bugs.webkit.org/show_bug.cgi?id=31550 and many others. On Fri, Apr 16, 2010 at 11:50 AM, Yong Li yong.li.web...@gmail.com wrote: Hi All The default implementation of JS Date is calling currentTime() (by jsCurrentTime()), so it assumes currentTime() returns current UTC time, and system UTC time can be changed. However, currentTime() is also used in most cases as a system tick count, which means it should always be monotonically increasing. I guess we should remove the dependency on currentTime() from JS Date to fix the confliction. -- --Antonio Gomes ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] currentTime() and UTC time
On Apr 19, 2010, at 7:11 PM, Holger Freyther wrote: I once had a patch to use clock_gettime but I discarded it as the call is slower than gettimeofday. I have a micro benchmark for that here[1]. Also tangentially related, I found an article about the lack of clock_gettime on Mac OS X. http://www.wand.net.nz/~smr26/wordpress/2009/01/19/monotonic-time-in-mac-os-x/ -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] currentTime() and UTC time
Hi All The default implementation of JS Date is calling currentTime() (by jsCurrentTime()), so it assumes currentTime() returns current UTC time, and system UTC time can be changed. However, currentTime() is also used in most cases as a system tick count, which means it should always be monotonically increasing. I guess we should remove the dependency on currentTime() from JS Date to fix the confliction. Any idea? -Yong ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
