- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Jan 2023 16:17:46 +0000
- To: public-webrtc-logs@w3.org
I might be mistaken here, but isn't the the sole purpose of the RTCICeCandidate constructor to create a candidate that will then be fed to RTCPeerConnectionIceEvent? If so, it would seem strange that we would design a half baked constructor and let it to JS to handle properties we do not deem useful enough. > I don't see any specs referencing these internal slots. Is any spec planning to? It is not specs. It is JS that can retrieve the value in different ways and the values will defer when shiming is used. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2795#issuecomment-1405254660 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 January 2023 16:17:48 UTC