** Changed in: webapps-sprint
Milestone: sprint-23 => sprint-24
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
** Changed in: webapps-sprint
Milestone: sprint-22 => sprint-23
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
** Changed in: location-service (Ubuntu)
Importance: Undecided => High
** Changed in: oxide
Status: In Progress => Invalid
** Changed in: webapps-sprint
Importance: Undecided => Critical
** Changed in: webapps-sprint
Importance: Critical => High
--
You received this bug
** Changed in: location-service (Ubuntu)
Status: New => In Progress
** Changed in: webapps-sprint
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
** Changed in: webapps-sprint
Milestone: sprint-21 => sprint-22
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
** Changed in: webapps-sprint
Milestone: sprint-20 => sprint-21
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
** Branch linked: lp:~mardy/location-service/old-location-1551686
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
To summarize the analysis and the plan forward, we have identified a
series of fixes and improvements to various parts of the stack:
Oxide: the ubuntu-specific provider code or related logic could filter
out obvious bogus values returned by the location-service which do not
meet the maximumAge
** Changed in: location-service (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Also affects: webapps-sprint
Importance: Undecided
Status: New
** Changed in: webapps-sprint
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: webapps-sprint
** Changed in: oxide
Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)
** Changed in: oxide
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
Oxide is normally also pulling updates once permission has been granted:
http://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/view/head:/qt/core/browser/oxide_qt_location_provider.cc#L352
Looking at that part, do you see something that would be at odds with
the logic in the other
I've been investigating the issue a bit. My understanding of the
situation is that Chromium (used by oxide) keeps its own cache for last
known location, and that's what it uses when the client plays with the
"maximumAge" option; otherwise, it assumes that the location provider
always returns new
According to the specification¹, when the 'maximumAge' parameter of a
call to getCurrentPosition() is not explicitly set, its value defaults
to 0, which instructs the user agent to request a new position, and not
return a cached one.
However pages that call getCurrentPosition() with a maximumAge
13 matches
Mail list logo
