[
https://issues.apache.org/jira/browse/CB-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-4703:
---------------------------------
Component/s: Plugin Geolocation
> geolocation Position.timestamp type is not consistent with W3C spec which API
> is based on
> -----------------------------------------------------------------------------------------
>
> Key: CB-4703
> URL: https://issues.apache.org/jira/browse/CB-4703
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS, Docs, Plugin Geolocation
> Affects Versions: 2.9.0
> Environment: Samsung Galaxy tablet - Android 4.0.3
> Reporter: Peter
> Assignee: Shazron Abdullah
> Priority: Minor
> Fix For: 3.4.0
>
>
> The geolocation API guide
> http://cordova.apache.org/docs/en/3.0.0/cordova_geolocation_geolocation.md.html#Geolocation
> says that the
> Cordova _API only executes on devices that don't already provide an
> implementation of_ http://dev.w3.org/geo/api/spec-source.html
> That W3C spec says that the Position.timestamp is a represented as a
> *DOMTimeStamp*
> Ref: http://dev.w3.org/geo/api/spec-source.html#position_interface
> And DOMTimeStamp is the behaviour that I observe when execute on my device
> (Samsung Galaxy Tab - Android 4.0.3).
> But this conflicts with:
> * Cordova API guide
> http://cordova.apache.org/docs/en/3.0.0/cordova_geolocation_geolocation.md.html#Position
> which says the Position timestamp is a *Date*
> * cordova.js geolocation Position, getCurtrentPosition etc which seems to be
> converting the DOMTimeStamp to a *Date*
> Shouldn't the geolocation API and cordova.js impl be consistent with the W3C
> spec which the guide says it is based on?
> See also CB-4596
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
