[
https://issues.apache.org/jira/browse/CB-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765428#comment-17765428
]
ASF subversion and git services commented on CB-11462:
------------------------------------------------------
Commit 13f2a203c4c6194da2feb5e5f41241fb8ce3a7bc in cordova-plugin-geolocation's
branch refs/heads/master from Norman Breau
[
https://gitbox.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=13f2a20 ]
fix: heading speed w3c spec (#270)
* CB-11462: (all) Make sure Coordinates#speed follows the w3c specification.
Speed can have a negative value on iOS devices when the OS is not able to
determine the current speed.
This is against the w3c specification. Which only allows null and a number
value >= 0.
See the following links for further informations:
* https://dev.w3.org/geo/api/spec-source.html#speed
*
https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocation_Class/#//apple_ref/occ/instp/CLLocation/speed
* CB-11462: (all) Make sure Coordinates#heading follows the w3c specification.
Heading (course) can have a negative value on iOS devices when the OS is not
able to determine the current heading.
This is against the w3c specification. Which only allows null and a number
value >= 0 and <= 360.
See the following links for further informations:
* https://dev.w3.org/geo/api/spec-source.html#heading
*
https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocation_Class/#//apple_ref/occ/instp/CLLocation/course
---------
Co-authored-by: Malte Legenhausen <[email protected]>
> Coordinates heading and speed can be negative under iOS
> -------------------------------------------------------
>
> Key: CB-11462
> URL: https://issues.apache.org/jira/browse/CB-11462
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-geolocation
> Affects Versions: Master
> Reporter: Malte Legenhausen
> Priority: Major
>
> On iOS the values heading and speed can be negative values according to the
> documentation of CLLocation. These values are directly exposed by the
> Coordinates object, which leads to unwanted bahavior. According to the w3c
> specification these values are only allows to be null or greater 0.
> Following links for further informations:
> * https://dev.w3.org/geo/api/spec-source.html#heading
> * https://dev.w3.org/geo/api/spec-source.html#speed
> *
> https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocation_Class/#//apple_ref/occ/instp/CLLocation/course
> *
> https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocation_Class/#//apple_ref/occ/instp/CLLocation/speed
> I already provided a pull request:
> https://github.com/apache/cordova-plugin-geolocation/pull/77
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]