Pref on WebRTC by default

RESOLVED FIXED in mozilla21

Status

()

defect
RESOLVED FIXED
7 years ago
3 years ago

People

(Reporter: jesup, Assigned: jesup)

Tracking

(Blocks 1 bug, {dev-doc-needed})

Trunk
mozilla21
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(relnote-firefox 21+)

Details

(Whiteboard: [WebRTC], [blocking-webrtc+], [qa-])

Attachments

(1 attachment)

There will be a bunch of bugs blocking this (try to keep it to the highest bug in a chain of dependencies; if we're blocked by B, and A blocks B, don't generally bother having A block this as well.  This is not a hard-and-fast rule.

Doing this will require privacy and security reviews to be passed.
Is there currently a bug to make a pref?
media.peerconnection.enabled (defaults to true on alder)
Depends on: 797258
Whiteboard: [WebRTC], [blocking-webrtc+]
Depends on: 798178
No longer blocks: 694812

Updated

6 years ago
No longer depends on: 821884

Updated

6 years ago
Depends on: 825927

Updated

6 years ago
Depends on: 822197
Removing Bug 827985 because we don't believe there is a significant advantage to moving webrtc out of libxul beyond the patch for bug 833118, which has already landed.
No longer depends on: 827985

Updated

6 years ago
Depends on: 834100
No longer depends on: 834100
No longer depends on: 833219
Depends on: 833219
Depends on: 840344
Comment on attachment 708963 [details] [diff] [review]
enable PeerConnection by default

Looking for trivial r+ in order to be ready to "flip the bit" once we've resolved the blockers.
Attachment #708963 - Flags: review?(roc)
No longer depends on: 797258
No longer depends on: 834152
No longer depends on: 835283
Sounds like we should land this now, right?

Quick question - are you prefing this on by default in FF 21 or FF 22? That might affect when we land this and if an uplift is needed.
I think we should land this now (today). 

I'd love to pref this on for at least the Aurora cycle of 21 to get some extra testing from the Aurora population.  It's unclear if we'll be able to fix and uplift enough bugs (I realize we have around 50 blocker-webrtc+ bugs currently open) to keep the feature on when Fx21 goes to Beta.  (We probably won't be able to.)  But the extra test time and developer exposure in Aurora 21 would be very valuable to the feature IMO.  If at any point, it becomes problematic to keep the feature pref'd on in Aurora 21, we can disable it. but it would be great if we could keep it on through the end of the Aurora 21 cycle.  Randell and I are talking to Alex and Bhavana (release-drivers) about what makes the most sense.  Thoughts about this are welcome here.
https://hg.mozilla.org/mozilla-central/rev/584660a01e64
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Whiteboard: [WebRTC], [blocking-webrtc+] → [WebRTC], [blocking-webrtc+], [qa-]

Updated

6 years ago
relnote-firefox: --- → ?
Keywords: dev-doc-needed
Depends on: 846358
No longer depends on: 846358

Comment 10

6 years ago
I noticed that it's not pref'd on by default anymore in Aurora (21.0a2) or in Firefox Beta (21.0). Is this intentional? Can we hope for it to be pref'd on by default when 21 goes to production?
(In reply to Adam Ullman from comment #10)
> I noticed that it's not pref'd on by default anymore in Aurora (21.0a2) or
> in Firefox Beta (21.0). Is this intentional? Can we hope for it to be pref'd
> on by default when 21 goes to production?

Yes, it's intentional. We preffed off for Fx21 because the feature isn't ready for production.

We're riding the trains to Fx22 for turning this feature on now.
(In reply to Jason Smith [:jsmith] from comment #11)
> Yes, it's intentional. We preffed off for Fx21 because the feature isn't
> ready for production.

Right, we had it preffed on in Aurora to enable wider testing, but the plan was to pref off before 21 went to Beta. See bug 853106.
Yes, our plan is to keep the feature pref'd on in Firefox 22 into production.

Comment 14

6 years ago
Thanks for the clarification.

Is there a way in JavaScript to detect whether the pref is on? Currently we're using 

  typeof(mozRTCPeerConnection) === 'function'

but that returns true even if the preference isn't on. It seems that the PeerConnection object is there it just doesn't work.

Comment 15

6 years ago
Sorry, just realised I can try/catch around new mozRTCPeerConnection. Should have tried that before posting.
Blocks: 1050930
You need to log in before you can comment on or make changes to this bug.