-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update and complete RTCPeerConnection #1288
Comments
It looks as though there was some unfortunate copy-and-paste somewhere, for instance I noticed that the information about RTCPeerConnection.getSenders was not correct, see #1713. I'll check if I find any other errors. |
RTCPeerConnection.getReceivers was also wrong, see #1714. |
|
Looks like there is only https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/currentRemoteDescription#Browser_compatibility left to migrate here. |
This was fixed in #2662 |
There has been a massive PR to add RTCPeerConnection (#1070), a few things were left out which we should add:
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/close
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/addTransceiver
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/currentRemoteDescription
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/iceGatheringState
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/onicecandidateerror
(we could also wait until we've initially updated the MDN pages [which will happen soon] and then update/correct this file for other issues found.)
The text was updated successfully, but these errors were encountered: