While I agree with your technical assessment of `addTrack`/`removeTrack` , the question is what action we are trying to encourage by marking these APIs as legacy. Are we saying that implementing those APIs is optional? Or that browsers that have not already shipped them should consider removing them from their future plans? As Harald says, if there is deployed code depending on those APIs, either of those actions will impact developers negatively. Developers such as @fippo have already given us some feedback about the costs of the stream -> track transition. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1758#issuecomment-362382171 using your GitHub accountReceived on Thursday, 1 February 2018 19:52:32 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC