Refinements to media permissions API

Bug #1461600 reported by Chris Coulson on 2015-06-03
18
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Oxide
High
Chris Coulson
1.8
High
Chris Coulson

Bug Description

The current API allows setting the camera / microphone per permission request. This implies that we need to persist the choice of media devices when we have content settings.

Whilst this is quite flexible, it will make it difficult to implement a simple settings UI in the browser to select the camera / microphone for websites to use (see Chrome's Preferences -> Content Settings -> Media).

I'm proposing the following changes:

- Remove OxideQMediaAccessPermissionRequest::allow(const QString&, const QString&)
- Add WebContext.videoCaptureDeviceId and WebContext.audioCaptureDeviceId, or something like that

Changed in oxide:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.9
Changed in oxide:
status: Triaged → Fix Released
Chris Coulson (chrisccoulson) wrote :

The changes for this were quite intrusive. For 1.8, I'm going to do the first part but not the second part. This should be ok for an initial implementation in the browser - Oxide will use the default audio capture device in pulseaudio and will select whichever camera is detected first (fine for the most common case where there's one camera - and the camera part doesn't yet work on the phone anyway)

Olivier Tilloy (osomon) wrote :

Now that the camera part works well in oxide and that we support devices with multiple cameras (the BQ Aquaris E4.5 has a front camera and a rear camera), it’d be good to implement the second part. Should I re-open this bug, or file a new one?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers