[
https://issues.apache.org/jira/browse/CB-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887169#comment-13887169
]
Peter commented on CB-4596:
---------------------------
Why add JIRA component for "Geolocation" but not the other ones? This issue is
regarding documentation consistency across multiple features.
> Documentation is not consistent for timestamp types
> ---------------------------------------------------
>
> Key: CB-4596
> URL: https://issues.apache.org/jira/browse/CB-4596
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs, Plugin Geolocation
> Affects Versions: 2.9.0
> Reporter: Peter
> Assignee: Michael Brooks
> Priority: Minor
>
> Compare Codova documentation for these timestamps:
> * Accelerometer > *Acceleration.timestamp* - _timestamp: Creation timestamp
> in milliseconds. (DOMTimeStamp)_
> * Compass > *CompassHeading.timestamp* - _timestamp: The time at which this
> heading was determined. (milliseconds)_
> * Geolocation > *Position.timestamp* - _timestamp: Creation timestamp for
> coords. (Date)_
> It is confusing that documentation describes all these "timestamps" to have
> different types.
> On closer inspection, for some reason the Position.timestamp really is
> (inconsistent with the others) returned as a Date object.
> But at least Acceleration/Compass ones seem to have same units so perhaps the
> documentation for those ones ought to consistently say they are DOMTimeStamp.
> Ref http://dev.w3.org/2006/webapi/WebIDL/#common-DOMTimeStamp
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
