ubuntu-webapps-bugs team mailing list archive

[Launchpad Bug Tracker <1604446@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

A browser based application that wants to use position can call getCurrentPosition
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/getCurrentPosition
or watchPosition
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/watchPosition

maps (such as google maps) and navigation applications will typically use watchPosition which will cause location services to turn on the GPS chip and get a new location for the device.
non-map applications that just want location aware context for things such as weather or local stores e.g. https://www.aldi.co.uk/store-finder do not subscribe to updates with watchPosition. They just call getCurrentPosition and expect a decent enough position to use.

Ubuntu Touch returns the last known position from the cache when
getCurrentPosition is called, and then fails to turn on the GPS. It
should block until it has a decent position and return good data to the
success callback. It certainly shouldn't return a bad position and then
fail to make an effort to get a good position.

The result of this bug is that you can go to a location aware web page,
it will think you are somewhere else entirely, and refreshing will not
improve the situation, you have to open a mapping application that uses
watchPosition and wait for a fix to be obtained before going back to
your location aware web page and refreshing to get good data.

** Affects: location-service (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: oxide
     Importance: Undecided
         Status: New

-- 
getcurrentPosition in oxide does not cause a wake up of the GPS
https://bugs.launchpad.net/bugs/1604446
You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide.