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: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Jan 2017 14:06:35 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-269976768-1483365994-sysbot+gh@w3.org>
I agree with @foolip. Most scripts still use the explicit 
`RTCIceCandidate` constructor since most browsers still require it 
(few know adapter.js removes the need for it).

Even scripts that stringify whatever comes out of `onicecandidate` 
would throw in a connection between an old and a new browser, due to 
signaling. E.g. between Chrome and Firefox, unless we implemented 
ufrag at the same time and eradicate all old versions.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/983#issuecomment-269976768 
using your GitHub account
Received on Monday, 2 January 2017 14:06:41 UTC

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