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

[webrtc-pc] Should we specify how addStream()/"addstream event" should behave?

From: Adam Bergkvist via GitHub <sysbot+gh@w3.org>
Date: Wed, 06 Apr 2016 09:15:00 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-146245996-1459934099-sysbot+gh@w3.org>
adam-be has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Should we specify how addStream()/"addstream event" should behave? 
==
The addStream()/"addstream event" API is widely adopted; it has much 
better browser support than the new addTrack()/addTranceiver() APIs. 
The intention is that the old API should be polyfilled using supported
 API points.

We currently specify how, for example, the legacy callback version of 
createOffer() should behave. The question is if we need to do the same
 for the addStream()/"addstream event" API to avoid uncertainties 
like:
* Which version of the API should be supported? Is it OK to say the 
last spec where it was present?
* The "addstream event" is not trivial to polyfill.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/568 using your GitHub account
Received on Wednesday, 6 April 2016 09:15:02 UTC

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