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: Thu, 23 Mar 2017 16:31:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-288778386-1490286670-sysbot+gh@w3.org>
Most specs have some bits of API that aren't yet implemented everywhere without that being considered a spec violation, so in that way implementations are already free to prioritize implementing other things over the callback-based APIs.

But the interesting question to me is what implementers want to do, and how to [find a path to interop](https://docs.google.com/document/d/1LSuLWJDP02rlC9bOlidL6DzBV5kSkV5bW5Pled8HGC8/edit?usp=sharing). Of the methods in https://w3c.github.io/webrtc-pc/#legacy-interface-extensions, are there any that *aren't* already supported everywhere that RTCPeerConnection itself is?

GitHub Notification of comment by foolip
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1086#issuecomment-288778386 using your GitHub account
Received on Thursday, 23 March 2017 16:31:18 UTC

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