Public bug reported:
Since bug 1428754 landed, applications have no way to know whether
geolocation and / or media devices are being accessed or blocked once
the initial permission has been set. This will only get worse when we
have peristent (ie, between sessions) storage of content settings.
We need to expand WebView.blockedContent and add the inverse
(WebView.allowedContent ?), which is what this property was added for.
This can be used by the application to indicate eg, whether a site is
using the microphone or whether a site has been denied access to
geolocation.
** Affects: oxide
Importance: High
Status: Triaged
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Status: New => Triaged
--
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/1470462
Title:
Provide a mechanism to indicate when geolocation / media access is in
use
Status in Oxide Webview:
Triaged
Bug description:
Since bug 1428754 landed, applications have no way to know whether
geolocation and / or media devices are being accessed or blocked once
the initial permission has been set. This will only get worse when we
have peristent (ie, between sessions) storage of content settings.
We need to expand WebView.blockedContent and add the inverse
(WebView.allowedContent ?), which is what this property was added for.
This can be used by the application to indicate eg, whether a site is
using the microphone or whether a site has been denied access to
geolocation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1470462/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp