[Ubuntu-webapps-bugs] [Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

2016-08-19 Thread Launchpad Bug Tracker 
This bug was fixed in the package location-service -
3.0.0+16.10.20160811-0ubuntu1

---
location-service (3.0.0+16.10.20160811-0ubuntu1) yakkety; urgency=medium

  [ Alberto Mardegan ]
  * Don't sent last known position to new sessions (LP: #1604446)

  [ Scott Sweeny ]
  * Enable running location-service on Snappy Ubuntu Core

  [ Thomas Voß ]
  * Make sure that we are not racing with the timeout handler.

 -- Thomas Voß   Thu, 11 Aug 2016 08:27:10
+

** Changed in: location-service (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1604446

Title:
  getcurrentPosition in oxide does not cause a wake up of the GPS

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  New
Status in webapps-sprint:
  New
Status in location-service package in Ubuntu:
  Fix Released

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604446/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-webapps-bugs] [Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

2016-08-17 Thread Jean-Baptiste Lallement 
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

** Changed in: canonical-devices-system-image
Milestone: None => 13

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1604446

Title:
  getcurrentPosition in oxide does not cause a wake up of the GPS

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  New
Status in webapps-sprint:
  New
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604446/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-webapps-bugs] [Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

2016-07-20 Thread David Barth 
** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
Milestone: None => sprint-25

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1604446

Title:
  getcurrentPosition in oxide does not cause a wake up of the GPS

Status in Oxide:
  New
Status in webapps-sprint:
  New
Status in location-service package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-webapps-bugs] [Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

2016-07-19 Thread Olivier Tilloy 
** Package changed: webbrowser-app (Ubuntu) => oxide

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1604446

Title:
  getcurrentPosition in oxide does not cause a wake up of the GPS

Status in Oxide:
  New
Status in location-service package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1604446/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp