- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jul 2018 01:57:19 +0000
- To: public-webrtc-logs@w3.org
@fippo What do you recommend that we do here? If possible, I'd prefer not to repeat the mistakes we made with the deprecation of the legacy streams API. For example, before marking addTrack/removeTrack as supplanted, don't we need to have more implementations of addTransceiver with test results showing consistent behavior? Also, if we have evidence that developers are using addTrack/removeTrack, don't we have the obligation to clearly specify it? While we might *believe* that addTransceiver will be better for developers, do we have enough data to indicate that it is strongly preferred on browsers that support it? -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1758#issuecomment-404020065 using your GitHub account
Received on Wednesday, 11 July 2018 01:57:22 UTC