- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 May 2017 09:23:20 +0000
- To: public-webrtc-logs@w3.org
@taylor-b, happy to hear that `new RTCIceCandidate({ candidate: '' })` won't throw exceptions in Chrome for long, it makes no sense to distinguish between that and `new RTCIceCandidate({})` when candidate's default value is the empty string.
My main point in this bug is that *no engine* currently requires one of sdpMid/sdpMLineIndex to be present, and adding that requirement comes with a compat risk, as any code in the wild that doesn't include one of these will start throwing. Perhaps there's a very good reason for that, but at first glance it seems better to just align the spec with what is already shipping.
--
GitHub Notification of comment by foolip
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1166#issuecomment-301028431 using your GitHub account
Received on Friday, 12 May 2017 09:23:26 UTC