Browser does not store permission for location access

[Pat McGowan]

Go to google.com
You are prompted to allow access to current location
Grant access
Refresh the page
You are prompted again

[Olivier Tilloy (osomon)]

Note that the system-wide trust store is already used for this for webapps. The browser app runs unconfined though. If it ran confined, the user would get a system prompt that would request location access on behalf of the browser, without specifying which website actually requests the information.

Also note that the current design doesn’t use the system-wide prompt, but instead has it integrated in the webview: https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g183c60488_08.

[Olivier Tilloy (osomon)]

Storage of site-specific settings belong in Oxide (see https://blueprints.launchpad.net/oxide/+spec/site-settings, and https://docs.google.com/document/d/1EZV4KzrH9eEUMjh3G8Cdykw3JTBtqOlunEEZd1kothA/edit).

[Olivier Tilloy (osomon)]

Note: the original bug description is not valid any longer: oxide now remembers permissions granted for the duration of the current browsing session, so refreshing the page won’t prompt the user for the permission again. However the permissions are not remembered across sessions, so closing the browser and opening it again will result in the user being prompted again.