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

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

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Thu, 13 Apr 2017 16:52:57 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-221622501-1492102376-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/webrtc-pc:

== Should the spec describe addStream/onaddstream as legacy API? ==
Related discussion in https://github.com/w3c/web-platform-tests/issues/5533

addStream and onaddstream are widely used but not specified in the WebRTC specification.
This API is more convenient to use from a web developer point of view for simple A/V calls then addTrack/ontrack.
This API is available in Edge, Chrome and Firefox while addTrack is only supported in Firefox.

>From a pragmatic point of view, it seems like the webrtc spec should describe this legacy API, in terms of existing API like addTrack for instance.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125 using your GitHub account
Received on Thursday, 13 April 2017 16:53:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC