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:42:09 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-289743670-1490701327-sysbot+gh@w3.org>
https://jsbin.com/coqibewate/edit?html,output is a test for existence of the callback-based `createOffer()` that passes in Chrome, Edge (with the "WebRTC 1.0" enabled), Firefox.

In order to remove the callback-based `createOffer()` (or ship `RTCPeerConnection` without it) I would try to understand the usage a bit first. There's actually a use counter for this in Blink which is pretty high: https://www.chromestatus.com/metrics/feature/timeline/popularity/1047

I didn't investigate any of the other methods, but this one seems like a risky undertaking and the upside isn't obvious to me. But I am not the Blink developer that would need to be convinced, just weighing in :)

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

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