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

Re: [webrtc-pc] RTCIceCandidateInit's required DOMString ufrag will throw for all existing content

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Jan 2017 10:26:04 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-272410507-1484303162-sysbot+gh@w3.org>
Thanks for fixing, @taylor-b!

> I still would find it helpful to know the general policy on 
backwards compatibility though

I can't speak for the WebRTC WG, but in all web standards work the 
approach I take is to ask "can this be implemented and shipped by 
everyone?" And to answer that question, one has to look into existing 
usage of an API, and whether some browsers might be constrained by web
 compat in ways that others are not, e.g. due to engine-specific code 
paths.

-- 
GitHub Notification of comment by foolip
Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/983#issuecomment-272410507 
using your GitHub account
Received on Friday, 13 January 2017 10:26:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:41 UTC