[Webkit-unassigned] [Bug 54529] GeolocationPosition to store timestamp as integer in miliseconds

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=54529





--- Comment #3 from Jarred Nicholls <jarred.nicholls at gmail.com>  2011-02-16 04:59:00 PST ---
(In reply to comment #2)
> Well remembered, Steve. I did ask Sam about this issue in an email, and he told me that it made more sense to use double in the C (as opposed to DOM)  APIs since that is what has been historically used.
> 
> Are there any examples of WebCore using integer milliseconds in non-DOM classes ?

Using a double for style reasons sounds fine to me.  I think a different question is, are there any examples of WebCore storing seconds in non-DOM classes where it is actually maintaining (dealing with) milliseconds internally or in the DOM?  And why?

Just wondering if GeolocationPosition is holding the timestamp in seconds for style reasons as well, or can we avoid the conversion from ms -> sec -> ms.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.