[
https://issues.apache.org/jira/browse/CB-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977357#comment-14977357
]
ASF subversion and git services commented on CB-4596:
-----------------------------------------------------
Commit 298abb9fc1c1695066c6783f7d1b8e6addd94dd5 in
cordova-plugin-device-orientation's branch refs/heads/master from
[~purplecabbage]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device-orientation.git;h=298abb9
]
CB-4596 Fix timestamp to be DOMTimeStamp across the board
> 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 Device Motion, Plugin Device Orientation,
> Plugin Geolocation
> Affects Versions: 2.9.0
> Reporter: Peter
> Assignee: Jesse MacFadyen
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
