You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Becky Gibson (JIRA)" <ji...@apache.org> on 2012/06/05 21:21:22 UTC
[jira] [Resolved] (CB-866) Position.timestamp treated
inconsistently
[ https://issues.apache.org/jira/browse/CB-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Becky Gibson resolved CB-866.
-----------------------------
Resolution: Fixed
resolved with this commit: https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-js.git;a=commit;h=109b8649b0e98597b147842a6f71999d2f7910f2
> Position.timestamp treated inconsistently
> -----------------------------------------
>
> Key: CB-866
> URL: https://issues.apache.org/jira/browse/CB-866
> 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 (http://www.w3.org/TR/geolocation-API/#position_interface).
> Discussed on list in thread beginning here: http://mail-archives.apache.org/mod_mbox/incubator-callback-dev/201206.mbox/%3CCAM1AYQCyqNd9pqn1eVmOb5smM37juNXvZKeH_SxXmxAWSnCPpw@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira