Becky Gibson created CB-866:
-------------------------------
Summary: 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_sxxmxawsnc...@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
