Permission request handling

Bug #1214037 reported by Chris Coulson on 2013-08-19
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Oxide
High
Chris Coulson

Bug Description

We need to implement an API to allow Oxide to delegate permission requests to the embedder (think, camera / microphone access for WebRTC)

Changed in oxide:
importance: Undecided → High
status: New → Triaged
Changed in oxide:
assignee: nobody → Olivier Tilloy (osomon)
Olivier Tilloy (osomon) wrote :

For reference, in QtWebKit the QML WebView has a signal called experimental.onPermissionRequested, that passes a permission object with the following properties: type, origin, allow. type and origin are read-only, whereas allow can be set. Setting it triggers accepting/denying the permission request.

Olivier Tilloy (osomon) wrote :

For geolocation permissions, we need to implement a custom content::GeolocationPermissionContext that will be returned by BrowserContext::GetGeolocationPermissionContext().

Not sure about other types of permissions. QtWebKit currently only exposes geolocation and notification permissions, but there are probably more types of permissions that we want to expose.

David Barth (dbarth) on 2014-01-27
tags: added: desktop webapp-container
Olivier Tilloy (osomon) on 2014-05-07
Changed in oxide:
assignee: Olivier Tilloy (osomon) → Chris Coulson (chrisccoulson)
status: Triaged → In Progress
Olivier Tilloy (osomon) wrote :

Closing this bug as geolocation permission request handling is now implemented. Let’s open separate bugs to track other types of permission requests.

Changed in oxide:
status: In Progress → Fix Committed
Changed in oxide:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers