WebkitPeerConnection00 constructor replace by webkitRTCPeerConnection
See mail above from serge lachapelle
posted Oct 16, 2012 11:50 AM by Serge Lachapelle
Hi,
We are getting closer to having WebRTC reach stable. As I mentioned a while
back, we are trying to make the last big changes before this happens.
As such, we are now hiding the PeerConnection00 class behind a flag
(--enable-deprecated-peer-connection) both for Canary and M23 beta.
This won't be visible in the chrome://flags page and therefore can't be made to
stick; you have to launch chrome/chromium with the flag every time if you
require the old API.
This is a hassle and having you switch APIs is no fun. Rest assured that
changes going forward will be smaller and smaller... and thanks for all the
amazing feedback so far!
/Serge
Original issue reported on code.google.com by laurent.strullu.orange@gmail.com on 25 Oct 2012 at 1:07
Original issue reported on code.google.com by
laurent.strullu.orange@gmail.com
on 25 Oct 2012 at 1:07