W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Jul 2017 16:47:00 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-312692003-1499100419-sysbot+gh@w3.org>
@fippo @henbos FWIW I don't think it's worth making `addStream` add all or nothing in this edge case.

Since `addStream` is not in the spec, I gather browsers are free to handle legacy as they see fit. But I prefer the narrowest definition of "legacy code" here, which is code already written. I doubt much (if any) of it suffers from this problem.

Firefox has polyfilled `addStream` for [almost 3 years](https://hg.mozilla.org/mozilla-central/rev/50e64b3d2d88), so for our backwards compat I think it makes sense to stick with what we already have.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-312692003 using your GitHub account
Received on Monday, 3 July 2017 16:47:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC