- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Dec 2017 14:59:15 +0000
- To: public-webrtc-logs@w3.org
I hear two arguments here: 1. specify it so browsers don't accidentally break it implementing transceivers, and 2. Tracks are too hard for users. On the first one, I'd prefer leaving legacy to browsers here. We missed a timing regression, and have fixed it already. The second point doesn't seem to be about legacy. We already omit specifying `addStream` so we shouldn't specify `onaddstream` either IMHO. The point of the pivot to tracks was to make users think about tracks. Bringing onaddstream back would (still) seem to undermine that, or am I missing something? A good `ontrack` example might help though. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1705#issuecomment-353371801 using your GitHub account
Received on Thursday, 21 December 2017 14:59:22 UTC