- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Nov 2022 07:08:45 +0000
- To: public-webrtc-logs@w3.org
> I claim there's no web compat problem here Agree. Further I am not sure that the assumption that folks actually use toJSON or rely on it in production apps is true. I stopped relying on it after https://bugs.chromium.org/p/chromium/issues/detail?id=467471 and generally prefer explicit signaling. > Web compat here is that for: > JSON.stringify(candidate) — only candidate, sdpMid and sdpMLineIndex appear This is not [what the spec says](https://w3c.github.io/webrtc-pc/#methods-2) and we seem to lack a test. In Chrome usernameFragment is not serialized. And we are missing tests. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2795#issuecomment-1316479832 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 November 2022 07:09:04 UTC