Firefox 47 is now our Developer Edition version, and it's scheduled to go to Beta on April 18th and to Release on June 7th. Detailed WebRTC (plus Web Audio) release notes for Firefox 47 are here.
If anyone has any questions about the release, the notes, or possible bugs in the code, feel free to reach out to me directly.
Cheers,
-Maire
---------------------------------------------------
Recording:
Periodic blinking is fixed (See bug 1234230)
Fire error if mime type is unsupported (See bug 963238)
Recorded videos of longer than a few seconds would not play (See bug 1213775)
Clear screen and other privacy improvements to about:webrtc (See bug 1209252)
Make RTCRtpSender.setParameters return a promise. (See bug 1247622)
Add support for RTCRtpEncodingParameters.scaleResolutionDownBy (See bug 1244913)
Increase buffer sizes on older Windows to avoid packet loss at very high (HD) bitrates (bug 1217677); allow Jumbo ethernet frames when in e10s mode (bug 1252755)
MediaStream in video element doesn't guarantee video size on "loadedmetadata" (See bug 1240478)
Firefox always sends full band Opus audio even though the negotiation specifies wideband audio (bug 1249098); support negotiation of mono Opus (bug 818618). Also fixed no audio on browser side when Opus payload types in offer and answer do not match (bug 1221473).
High CPU usage on some systems when IPV6 interfaces are configured (See bug 1224845)
May i ask a question here?I know that Chrome version X corresponds to Webrtc version X.but what's the relationship between Firefox version and Webrtc version?
for example, i'm running a firefox 45.0.1 version, does this version using the code in Webrtc M45 release?
在 2016年3月24日星期四 UTC+8下午10:08:40,Maire Reavy写道:Firefox 47 is now our Developer Edition version, and it's scheduled to go to Beta on April 18th and to Release on June 7th. Detailed WebRTC (plus Web Audio) release notes for Firefox 47 are here.
If anyone has any questions about the release, the notes, or possible bugs in the code, feel free to reach out to me directly.
Cheers,
-Maire
---------------------------------------------------
Noteworthy Changes:
Recording:
Periodic blinking is fixed (See bug 1234230)
Fire error if mime type is unsupported (See bug 963238)
Recorded videos of longer than a few seconds would not play (See bug 1213775)
Clear screen and other privacy improvements to about:webrtc (See bug 1209252)
Make RTCRtpSender.setParameters return a promise. (See bug 1247622)
Add support for RTCRtpEncodingParameters.scaleResolutionDownBy (See bug 1244913)
Increase buffer sizes on older Windows to avoid packet loss at very high (HD) bitrates (bug 1217677); allow Jumbo ethernet frames when in e10s mode (bug 1252755)
MediaStream in video element doesn't guarantee video size on "loadedmetadata" (See bug 1240478)
Firefox always sends full band Opus audio even though the negotiation specifies wideband audio (bug 1249098); support negotiation of mono Opus (bug 818618). Also fixed no audio on browser side when Opus payload types in offer and answer do not match (bug 1221473).
High CPU usage on some systems when IPV6 interfaces are configured (See bug 1224845)
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/7eddccdb-d405-4218-ab9e-42879aa914a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/df0ad3ea-e3e0-4066-8801-ee9fec880bc9%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_KRGc9DH7haNs%3DGdtSMT89Fw%2BjM%3Dr0SZn_92tXsZvSQFg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CADxkKiJg25y8%3DD-KejV7%3DyG5aWFXS8LDqegibc6wULAqkLiHTA%40mail.gmail.com.
By the way, I am surprised you are using it (for anything other than tests), since specifications usually require multiple independent implementations. Using the same implementation may kind of prevent it from advancing to a candidate recommendation and the like.
Are you using the WebRTC.org code for anything other than tests? If so, what features are implemented using WebRTC.org code?
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_KRGc9DH7haNs%3DGdtSMT89Fw%2BjM%3Dr0SZn_92tXsZvSQFg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/57082D0A.7060801%40reavy.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_%2B8YfkxhxanvfMUwWwdgfjfO%3DapALKbaZfSm0pPvFMyvg%40mail.gmail.com.