Closed Bug 1281833 Opened 3 years ago Closed 3 months ago

Add webrtcUI WebExtension calls

Categories

(WebExtensions :: General, enhancement, P5)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: abr, Unassigned)

References

Details

(Whiteboard: [design-decision-approved] triaged)

Bug 1189060 added hooks into webrtcUI to allow addons control over certain aspects of the WebRTC permissions and consent model. The blog post at <https://hacks.mozilla.org/2015/09/controlling-webrtc-peerconnections-with-an-extension/> does a good job of demonstrating the kind of things that this facilitates.

The only way to use this at the moment is through traditional mechanisms; however, the utility of this API is likely to remain even after we start shepherding addons authors towards WebExtensions as a preferred technology.

This bug is intended to cover both design and implementation of a WebExtensions API that allows (among other things):
- The ability to add, remove, or change IP addresses exposed by PeerConnections
- Prompting the user for permission to perform address gathering and forming of connections, including the ability to block such operations altogether
- The ability to add user-visible indicia when various WebRTC conditions exist (basically, addons need to know when the various operations and connection states begin and end)

This is a short list off the top of my head; there are probably other things that I've overlooked.

Marking [design-decision-approved] at Andy's suggestion.
this is likely a good first bug for experiments (landing in Q3). let's use this to get some examples for others to follow.
Priority: -- → P2
Whiteboard: [design-decision-approved] → [design-decision-approved] triaged
Andrew is working on implementing this as an Experiment.
Assignee: nobody → aswan
Component: WebExtensions: Untriaged → WebExtensions: Experiments
Depends on: 1310355
Priority: P2 → P5
Product: Toolkit → WebExtensions

The experiment from comment 3 is now out of date but there hasn't been any serious interest in this. Unassigning myself as I'm not actively working on it.

Assignee: aswan → nobody

Another close/invalidate or push somewhere into planning bug.

Flags: needinfo?(philipp)
Component: Experiments → General

I'm inclined to close this bug until we encounter a more recent use case and request for accessing this kind of information. If anyone from the WebRTC team wants to get in touch with me on this please do.

Status: NEW → RESOLVED
Closed: 3 months ago
Flags: needinfo?(philipp)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.