incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Becky Gibson (JIRA)" <>
Subject [jira] [Resolved] (CB-866) Position.timestamp treated inconsistently
Date Tue, 05 Jun 2012 19:21:22 GMT


Becky Gibson resolved CB-866.

    Resolution: Fixed

resolved with this commit:;a=commit;h=109b8649b0e98597b147842a6f71999d2f7910f2
> Position.timestamp treated inconsistently
> -----------------------------------------
>                 Key: CB-866
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaJS
>    Affects Versions: 1.8.0
>            Reporter: Becky Gibson
>            Assignee: Becky Gibson
>             Fix For: 1.8.0
> Position.timestamp is inconsistent.   Code in getCurrentLocation will set it as the return
value from the platform (which is currently inconsistent as milliseconds or Date object) or
as a new Date().  Position constructor sets it as incoming value or Date().getTime().   Code
in getCurrentLocation treats it as a Date:  geolocation.lastPosition.timestamp.getTime().
> Needs to be made consistent as Date() object to comply with spec (

> Discussed on list in thread beginning here:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message