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

Re: [webrtc-pc] Make legacy API optional to implement

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Tue, 28 Mar 2017 11:12:32 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-289737531-1490699551-sysbot+gh@w3.org>
Are there any of these that can't be expressed in terms of the promise-vending variants? If so, would that be a problem for someone who tries to migrate from callbacks to promises?

There are indeed other APIs that are widely implemented and yet not in the spec. I consider such things in Blink to be bugs, and `onaddstream` specifically is tracked by [an issue to either standardize or remove](https://bugs.chromium.org/p/chromium/issues/detail?id=697059).

GitHub Notification of comment by foolip
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1086#issuecomment-289737531 using your GitHub account
Received on Tuesday, 28 March 2017 11:12:38 UTC

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