- From: Anne van Kesteren <annevk@opera.com>
- Date: Thu, 10 Jul 2008 07:22:38 +0200
- To: "Doug Turner" <doug.turner@gmail.com>, "Chris Prince" <cprince@google.com>
- Cc: "Innovimax SARL" <innovimax@gmail.com>, public-geolocation@w3.org
On Thu, 10 Jul 2008 03:06:27 +0200, Doug Turner <doug.turner@gmail.com> wrote: > Keeping it milliseconds matches the timestamp of the mouse event: > > timeStamp of type DOMTimeStamp, readonly > Used to specify the time (in milliseconds relative to the epoch) at > which the event was created. Due to the fact that some systems may not > provide this information the value of timeStamp may be not available for > all events. When not available, a value of 0 will be returned. Examples > of epoch time are the time of the system start or 0:0:0 UTC 1st January > 1970. > > I think we should be consistent here. That's fine, but that would still require changing the specification as it doesn't use DOMTimeStamp currently. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Thursday, 10 July 2008 05:23:11 UTC