- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 May 2024 16:02:05 +0000
- To: public-webrtc-logs@w3.org
I have a question related to this which was introduced in #574 after Chrome was just updated to "follow the spec" which [broke](https://issues.chromium.org/issues/337071657) because toJSON can no longer be called. * How is toJSON supposed to be used now? * How is returning a dictionary consistent with emitting a [candidate object in the iceevent](https://w3c.github.io/webrtc-pc/#rtcpeerconnectioniceevent)? I'll note that returning RTCSessionDescription has not been a problem for anyone for the last eight years despite Firefox and Safari not doing so. Most web developers who have been around for a while stopped trusting toJSON [after this issue](https://issues.chromium.org/issues/40409658) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/922#issuecomment-2090891060 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 May 2024 16:02:06 UTC