WebRTC was shipped with a prefix. Bug 1155923 moves our codebase to non-prefixed names, but includes a patch to restore aliases with the prefix. Thus we will expose `RTCPeerConnection` and use that ourselves, but permit legacy code to use `mozRTCPeerConnection`.
Maybe some day we can remove the aliases by just backing out the patch that creates prefixed aliases, but that seems unlikely in the short term [1][2]. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1155923 Link to standard: http://w3c.github.io/webrtc-pc/ Platform coverage: everywhere Target release: 43 Preference behind which this will be implemented: none DevTools bug: none Chrome and Opera ship with a 'webkit' prefix. I'm not aware of any shipping implementation of this API in other browsers. [1] Compatibility on the WebRTC API has been very poor in the past. I'm not aware of any code that doesn't detect browsers based on the prefixed names and then does something browser-specific. [2] However, this situation has been improving rapidly. In any case, a less-than perfect interoperability situation is no excuse for using prefixes. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
