[CB-866] Position.timestamp treated inconsistently

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.0
• Fix Version/s: 1.8.0
• Component/s: cordova-js
• Assignee: Becky Gibson
• Reporter: Becky Gibson
• Created: 05/Jun/12 18:08
• Updated: 23/Aug/18 07:35
• Resolved: 05/Jun/12 19:20

Description

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/[e-mail]%3E

Issue Links

• is depended upon by: CB-867 Update docs to indicate that Position.timestamp is a Date object
• is depended upon by: CB-868 Update geolocation tests for timestamp as Date