[webapps] Denying geolocation permission doesn’t inform the requester of the denial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Invalid
|
Undecided
|
Unassigned | ||
location-service |
Invalid
|
Undecided
|
Unassigned | ||
qtubuntu-sensors |
New
|
Undecided
|
Thomas Voß | ||
webbrowser-app |
Invalid
|
High
|
Unassigned |
Bug Description
Since version 0.23+14.
If the user denies permission however, the location service doesn’t seem to inform oxide of the denial, and the page keeps waiting for a geolocation update until it eventually times out, instead of informing the user right away that geolocation is not available.
This can easily be tested by running the following on a device:
webapp-
(make sure to wipe the trust store db in ~/.local/
I’m not sure whether the problem is in the location service itself, or in oxide.
Or is there a way for the webapp container to trigger and communicate with the trust store prompt?
Changed in webbrowser-app: | |
importance: | Undecided → High |
tags: | added: rtm14 |
Changed in qtubuntu-sensors: | |
assignee: | nobody → Thomas Voß (thomas-voss) |
tags: | added: touch-2014-09-25 |
Changed in location-service: | |
status: | New → Invalid |
The general flow of things is:
webbrowser-app <-> qtlocation <-> Ubuntu backend <-> platform api <-> location service <-> trust store
The location service returns an error message if the user denied access, see http:// bazaar. launchpad. net/~phablet- team/location- service/ trunk/view/ head:/src/ location_ service/ com/ubuntu/ location/ service/ skeleton. cpp#L172. However, the error report is not correctly handed up the stack on the client side. With that, I marked qtubuntu-sensors as affected, too.