About a week ago, the WebRTC team flipped the pref to turn WebRTC builds on by default in nightly, and yesterday navigator.mozGetUserMedia() landed in nightly. To enable these, the user must browse to about: config.

mozGetUserMedia is the only piece of WebRTC that a developer can really play with, and we expect that only a relatively small percentage of the Aurora user population will be using it in Firefox 16. However, WebRTC currently adds about 1.5MB to the Firefox footprint.

Although I'd like the feature to be as available as possible to devs and testers, I think it make sense to turn off building WebRTC by default when Firefox 16 uplifts to Aurora, and here's why:

 * The footprint increase is significant and for most users, they
   aren't getting much return for the increase.
 * We want developers and testers using the latest and greatest code
   (i.e. nightly) and having the feature in Aurora means there's the
possibility that some devs may develop and test against old code. And I can believe that the getUserMedia code Aurora will be quite
   stale within a few weeks of uplift.
 * We don't want the added burden of patching or fixing getUserMedia
   bugs found in Aurora.  We want to fix them in nightly and move on IMO.

Thoughts?

If we agree that it makes sense to flip the pref off when Firefox 16 uplifts next week, I'll file a bug and make the recommendation to the release-drivers.

Thanks!
-Maire

--
Maire Reavy <[email protected]>
Mozilla

_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media

Reply via email to