W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2022

Re: [webrtc-pc] Missing url in RTCIceCandidateInit (#2795)

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Thu, 01 Dec 2022 20:41:38 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1334420623-1669927297-sysbot+gh@w3.org>
> Also, am I right in thinking that all current implementations are actually supporting full fidelity?

from https://wpt.fyi/results/webrtc/toJSON.html is a great example of the disconnect between "what the working group thinks" and reality. This was not even covered by WPT.

"web developers" do not seem to care about usernameFragment in toJSON. I have not found a bug complaining about the lack of usernameFragment even and had to file one.

If you look at major opensource projects, Jitsi and MediaSoup don't even bother with the concept of using JSON strings for signaling. Janus has a healthy distrust for JSON.stringify (and toJSON) as evidenced [here](https://github.com/meetecho/janus-gateway/blob/972b2b4e3593019852cb8bf355ca6a0525f0d411/html/janus.js#L1894) because of past issues. Browser improved? However, as shown by the lack of WPT the lack of trust is very much justified.

GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2795#issuecomment-1334420623 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 20:41:40 UTC

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