Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: heading speed w3c spec #270

Merged
merged 2 commits into from
Sep 15, 2023

Commits on Sep 15, 2023

  1. CB-11462: (all) Make sure Coordinates#speed follows the w3c specifica…

    …tion.
    
    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
    Malte Legenhausen authored and breautek committed Sep 15, 2023
    Configuration menu
    Copy the full SHA
    0b6c059 View commit details
    Browse the repository at this point in the history
  2. CB-11462: (all) Make sure Coordinates#heading follows the w3c specifi…

    …cation.
    
    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
    Malte Legenhausen authored and breautek committed Sep 15, 2023
    Configuration menu
    Copy the full SHA
    e4bd983 View commit details
    Browse the repository at this point in the history