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

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

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Fri, 14 Apr 2017 06:13:38 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-294097801-1492150417-sysbot+gh@w3.org>
https://crbug.com/697059 is the tracking issue for this in Blink, where I also included getLocalStreams, getRemoteStreams and the MediaStreamEvent interface. (getStreamById is https://crbug.com/698163, and seems quite feasible to remove.)

I wrote these tests for existence: https://jsbin.com/qirujiq/edit?html,output

That shows that Chrome and Edge already ship all of these APIs, and Firefox ships everything except the removeStream method.

WebKit has everything except the onremovestream event handler attribute in their IDL:

We have use counters for most of this in Chrome:
* [addStream](https://www.chromestatus.com/metrics/feature/timeline/popularity/1641)
* [removeStream](https://www.chromestatus.com/metrics/feature/timeline/popularity/1646)
* [getLocalStreams](https://www.chromestatus.com/metrics/feature/timeline/popularity/1643)
* [getRemoteStreams](https://www.chromestatus.com/metrics/feature/timeline/popularity/1644)

I defer to @guidou @henbos to say what we'd prefer happen with these APIs.

GitHub Notification of comment by foolip
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-294097801 using your GitHub account
Received on Friday, 14 April 2017 06:13:45 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:40 UTC